Digital assistant hardware abstraction

ABSTRACT

This relates to intelligent automated assistants and, more specifically, to intelligent context sharing and task performance among a collection of devices with intelligent automated assistant capabilities. An example method includes, at a first electronic device participating in a context-sharing group associated with a first location: receiving a user voice input; receiving, from a context collector, an aggregate context of the context-sharing group; providing at least a portion of the aggregate context and data corresponding to the user voice input to a remote device; receiving, from the remote device, a command to perform one or more tasks and a device identifier corresponding to a second electronic device; and transmitting the command to the second electronic device based on the device identifier, wherein the command causes the second electronic device to perform the one or more tasks.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/990,876, entitled “DIGITAL ASSISTANT HARDWARE ABSTRACTION,” filedAug. 11, 2020, which claims priority to U.S. Provisional Application No.63/022,942, entitled “DIGITAL ASSISTANT HARDWARE ABSTRACTION,” filed May11, 2020, the contents of which are hereby incorporated by reference intheir entirety for all purposes.

FIELD

This relates generally to intelligent automated assistants and, morespecifically, to intelligent context sharing and task performance amonga collection of devices with intelligent automated assistantcapabilities.

BACKGROUND

Intelligent automated assistants (or digital assistants) can provide abeneficial interface between human users and electronic devices. Suchassistants can allow users to interact with devices or systems usingnatural language in spoken and/or text forms. For example, a user canprovide a speech input containing a user request to a digital assistantoperating on an electronic device. The digital assistant can interpretthe user's intent from the speech input and operationalize the user'sintent into tasks. The tasks can then be performed by executing one ormore services of the electronic device, and a relevant output responsiveto the user request can be returned to the user.

SUMMARY

A location, such as a home or an office, may contain multiple deviceswith digital assistant capabilities. It thus can be desirable for themultiple devices to share context information among one another so thatthe digital assistants of the multiple devices may intelligentlycoordinate the performance of tasks in response to user requests basedon, for example, events that are occurring (and that have recentlyoccurred) at each device, the location of users with respect to eachdevice, and/or what device capabilities the tasks require. In thismanner, a user-requested task may be performed at a device of themultiple devices even if a user does not directly provide a user requestto the digital assistant of that device. This in turn creates anappearance of a single digital assistant that interacts with a useracross the multiple devices, instead of multiple individual digitalassistants at each of the multiple devices.

Example methods are disclosed herein. An example method includes, at afirst electronic device: joining a context-sharing group associated witha first location, wherein the context-sharing group is a collection ofat least two electronic devices that each share context information withat least one other electronic device included in the collection, andwherein the collection includes at least a second electronic device.After joining the context-sharing group, electing one electronic deviceof the collection of at least two electronic devices as a contextcollector of the context-sharing group, wherein electing the contextcollector includes: determining a first context collector scorecorresponding to the first electronic device based at least on astrength of connectivity between the first electronic device and awireless network of the first location; receiving, from at least thesecond electronic device, one or more context collector scorescorresponding to at least the second electronic device; and determining,based on the first context collector score and the one or more contextcollector scores corresponding to at least the second electronic device,which electronic device of the electronic devices included in thecontext-sharing group to elect as the context collector of thecontext-sharing group. In accordance with a determination to elect thefirst electronic device as the context collector, receiving contextinformation from at least the second electronic device in response to atleast the second electronic device undergoing a device state change.

Another example method includes, at a first electronic deviceparticipating in a context-sharing group associated with a firstlocation, wherein the context-sharing group is a collection of at leasttwo electronic devices that each share context information with at leastone other electronic device included in the collection, and wherein thecollection includes at least a second electronic device and a contextcollector: receiving a user voice input; receiving, from the contextcollector, an aggregate context of the context-sharing group; afterreceiving the aggregate context, providing at least a portion of theaggregate context and data corresponding to the user voice input to aremote device that is not participating in the context-sharing group;receiving, from the remote device, a command to perform one or moretasks and a device identifier corresponding to the second electronicdevice, wherein the remote device determines the one or more tasks andthe device identifier based on the data corresponding to the user voiceinput and context information included in the at least a portion of theaggregate context; and transmitting the command to the second electronicdevice based on the device identifier, wherein the command causes thesecond electronic device to perform the one or more tasks.

Another example method includes, at one or more servers: receiving auser voice input and at least a portion of an aggregate context of acontext-sharing group associated with a first location from a firstelectronic device that is participating in the context-sharing group,wherein the context-sharing group is a collection of a plurality ofelectronic devices that each share context information with at least oneother electronic device included in the collection; determining a userintent based on the user voice input; determining one or more taskscorresponding to the user intent; identifying a second electronic deviceof the plurality of electronic devices to perform the one or more tasksbased on the one or more tasks and context information included in theat least a portion of the aggregate context; and transmitting, to thefirst electronic device, a command to perform the one or more tasks anda device identifier corresponding to the second electronic device,wherein the first electronic transmits the command to the secondelectronic device based on the device identifier, and wherein thecommand causes the second electronic device to perform the one or moretasks.

Another example method includes, at a first electronic deviceparticipating in a context-sharing group associated with a firstlocation, wherein the context-sharing group is a collection of aplurality of electronic devices that each share context information withat least one other electronic device included in the collection, andwherein the collection includes a context collector: receiving a uservoice input; receiving, from the context collector, an aggregate contextof the context-sharing group; after receiving the aggregate context,providing at least a portion of the aggregate context and datacorresponding to the user voice input to a remote device that is notparticipating in the context-sharing group, wherein the remote devicedetermines a plurality of tasks based on the data corresponding to theuser voice input; receiving, from the remote device: a first command toperform a first set of tasks of the plurality of tasks and a secondcommand to perform a second set of tasks of the plurality of tasks; anda first device identifier corresponding to a second electronic device ofthe plurality of electronic devices and a second device identifiercorresponding to a third electronic device of the plurality ofelectronic devices; transmitting the first command to the secondelectronic device based on the first device identifier, wherein thefirst command causes the second electronic device to perform the firstset of tasks; and transmitting the second command to the thirdelectronic device based on the second device identifier, wherein thesecond command causes the third electronic device to perform the secondset of tasks.

Another example method includes, at a system including at least a firstelectronic device and a second electronic device that are participatingin a context-sharing group associated with a first location, wherein thecontext-sharing group is a collection of at least two electronic devicesthat each share context information with at least one other electronicdevice included in the collection, and wherein the collection includes acontext collector: receiving, at the first electronic device, a firstuser voice input; outputting, at the first electronic device, a firstdigital assistant response based on the first user voice input, whereinthe first electronic device transmits context information including adigital assistant dialog session history for the first electronic deviceto the context collector after outputting the first digital assistantresponse; receiving, at the second electronic device, a second uservoice input; receiving, at the second electronic device, an updatedaggregate context of the context-sharing group from the contextcollector, wherein the updated aggregate context includes the digitalassistant dialog session history for the first electronic device; andoutputting, at the second electronic device, a second digital assistantresponse based on the second user voice input and the digital assistantdialog history for the first electronic device.

Another example method includes, at a first electronic deviceparticipating in a context-sharing group associated with a firstlocation, wherein the context-sharing group is a collection of at leasttwo electronic devices that each share context information with at leastone other electronic device participating in the collection, and whereinthe collection includes at least a second electronic device and acontext collector: receiving a user voice input, wherein the user voiceinput includes a digital assistant trigger; in response to detecting thedigital assistant trigger, transmitting a first trigger advertisement tothe context collector, wherein the first trigger advertisement indicatesa first time at which the digital assistant trigger ended according tothe first electronic device; receiving, from the context collector, asecond trigger advertisement, wherein the second trigger advertisementindicates a second time at which the digital assistant trigger endedaccording to the second electronic device; determining whether thesecond time is within a predetermined time range before the first time;and in accordance with a determination that the second time is withinthe predetermined time range before the first time, forgoing furtherprocessing of the user voice input.

Example non-transitory computer-readable media are disclosed herein. Anexample non-transitory computer-readable storage medium stores one ormore programs. The one or more programs comprise instructions, whichwhen executed by one or more processors of a first electronic device,cause the first electronic device to: join a context-sharing groupassociated with a first location, wherein the context-sharing group is acollection of at least two electronic devices that each share contextinformation with at least one other electronic device included in thecollection, and wherein the collection includes at least a secondelectronic device; after joining the context-sharing group, elect oneelectronic device of the collection of at least two electronic devicesas a context collector of the context-sharing group, wherein electingthe context collector includes: determining a first context collectorscore corresponding to the first electronic device based at least on astrength of connectivity between the first electronic device and awireless network of the first location; receiving, from at least thesecond electronic device, one or more context collector scorescorresponding to at least the second electronic device; and determining,based on the first context collector score and the one or more contextcollector scores corresponding to at least the second electronic device,which electronic device of the electronic devices included in thecontext-sharing group to elect as the context collector of thecontext-sharing group; and in accordance with a determination to electthe first electronic device as the context collector, receive contextinformation from at least the second electronic device in response to atleast the second electronic device undergoing a device state change.

Another example non-transitory computer-readable storage medium storesone or more programs, the one or more programs comprising instructions,which when executed by one or more processors of a first electronicdevice, cause the first electronic device to: while the first electronicdevice is participating in a context-sharing group associated with afirst location, wherein the context-sharing group is a collection of atleast two electronic devices that each share context information with atleast one other electronic device included in the collection, andwherein the collection includes at least a second electronic device anda context collector: receive a user voice input; receive, from thecontext collector, an aggregate context of the context-sharing group;after receiving the aggregate context, provide at least a portion of theaggregate context and data corresponding to the user voice input to aremote device that is not participating in the context-sharing group;receive, from the remote device, a command to perform one or more tasksand a device identifier corresponding to the second electronic device,wherein the remote device determines the one or more tasks and thedevice identifier based on the data corresponding to the user voiceinput and context information included in the at least a portion of theaggregate context; and transmit the command to the second electronicdevice based on the device identifier, wherein the command causes thesecond electronic device to perform the one or more tasks.

Another example non-transitory computer-readable storage medium storesone or more programs, the one or more programs comprising instructions,which when executed by one or more processors of one or more servers,cause the one or more servers to: receive a user voice input and atleast a portion of an aggregate context of a context-sharing groupassociated with a first location from a first electronic device that isparticipating in the context-sharing group, wherein the context-sharinggroup is a collection of a plurality of electronic devices that eachshare context information with at least one other electronic deviceincluded in the collection; determine a user intent based on the uservoice input; determine one or more tasks corresponding to the userintent; identify a second electronic device of the plurality ofelectronic devices to perform the one or more tasks based on the one ormore tasks and context information included in the at least a portion ofthe aggregate context; and transmit, to the first electronic device, acommand to perform the one or more tasks and a device identifiercorresponding to the second electronic device, wherein the firstelectronic transmits the command to the second electronic device basedon the device identifier, and wherein the command causes the secondelectronic device to perform the one or more tasks.

Another example non-transitory computer-readable storage medium storesone or more programs, the one or more programs comprising instructions,which when executed by one or more processors of a first electronicdevice, cause the first electronic device to: while the first electronicdevice is participating in a context-sharing group associated with afirst location, wherein the context-sharing group is a collection of aplurality of electronic devices that each share context information withat least one other electronic device included in the collection, andwherein the collection includes a context collector: receive a uservoice input; receive, from the context collector, an aggregate contextof the context-sharing group; after receiving the aggregate context,provide at least a portion of the aggregate context and datacorresponding to the user voice input to a remote device that is notparticipating in the context-sharing group, wherein the remote devicedetermines a plurality of tasks based on the data corresponding to theuser voice input; receive, from the remote device: a first command toperform a first set of tasks of the plurality of tasks and a secondcommand to perform a second set of tasks of the plurality of tasks; anda first device identifier corresponding to a second electronic device ofthe plurality of electronic devices and a second device identifiercorresponding to a third electronic device of the plurality ofelectronic devices; transmit the first command to the second electronicdevice based on the first device identifier, wherein the first commandcauses the second electronic device to perform the first set of tasks;and transmit the second command to the third electronic device based onthe second device identifier, wherein the second command causes thethird electronic device to perform the second set of tasks.

A non-transitory computer-readable storage medium storing one or moreprograms, the one or more programs comprising instructions, which whenexecuted by one or more processors of a first electronic device, causethe first electronic device to: while a first electronic device and asecond electronic device are participating in a context-sharing groupassociated with a first location, wherein the context-sharing group is acollection of at least two electronic devices that each share contextinformation with at least one other electronic device included in thecollection, and wherein the collection includes a context collector:receive, at the first electronic device, a first user voice input;output, at the first electronic device, a first digital assistantresponse based on the first user voice input, wherein the firstelectronic device transmits context information including a digitalassistant dialog session history for the first electronic device to thecontext collector after outputting the first digital assistant response;receive, at the second electronic device, a second user voice input;receive, at the second electronic device, an updated aggregate contextof the context-sharing group from the context collector, wherein theupdated aggregate context includes the digital assistant dialog sessionhistory for the first electronic device; and output, at the secondelectronic device, a second digital assistant response based on thesecond user voice input and the digital assistant dialog history for thefirst electronic device.

A non-transitory computer-readable storage medium storing one or moreprograms, the one or more programs comprising instructions, which whenexecuted by one or more processors of a first electronic device, causethe first electronic device to: while the first electronic device isparticipating in a context-sharing group associated with a firstlocation, wherein the context-sharing group is a collection of at leasttwo electronic devices that each share context information with at leastone other electronic device participating in the collection, and whereinthe collection includes at least a second electronic device and acontext collector: receive a user voice input, wherein the user voiceinput includes a digital assistant trigger; in response to detecting thedigital assistant trigger, transmit a first trigger advertisement to thecontext collector, wherein the first trigger advertisement indicates afirst time at which the digital assistant trigger ended according to thefirst electronic device; receive, from the context collector, a secondtrigger advertisement, wherein the second trigger advertisementindicates a second time at which the digital assistant trigger endedaccording to the second electronic device; determine whether the secondtime is within a predetermined time range before the first time; and inaccordance with a determination that the second time is within thepredetermined time range before the first time, forgo further processingof the user voice input.

Example electronic devices and systems are disclosed herein. An examplefirst electronic device comprises one or more processors; a memory; andone or more programs, where the one or more programs are stored in thememory and are configured to be executed by the one or more processors,the one or more programs including instructions for: joining acontext-sharing group associated with a first location, wherein thecontext-sharing group is a collection of at least two electronic devicesthat each share context information with at least one other electronicdevice included in the collection, and wherein the collection includesat least a second electronic device. After joining the context-sharinggroup, electing one electronic device of the collection of at least twoelectronic devices as a context collector of the context-sharing group,wherein electing the context collector includes: determining a firstcontext collector score corresponding to the first electronic devicebased at least on a strength of connectivity between the firstelectronic device and a wireless network of the first location;receiving, from at least the second electronic device, one or morecontext collector scores corresponding to at least the second electronicdevice; and determining, based on the first context collector score andthe one or more context collector scores corresponding to at least thesecond electronic device, which electronic device of the electronicdevices included in the context-sharing group to elect as the contextcollector of the context-sharing group. In accordance with adetermination to elect the first electronic device as the contextcollector, receiving context information from at least the secondelectronic device in response to at least the second electronic deviceundergoing a device state change.

Another example first electronic device comprises one or moreprocessors; a memory; and one or more programs, where the one or moreprograms are stored in the memory and are configured to be executed bythe one or more processors, the one or more programs includinginstructions for: while the first electronic device is participating ina context-sharing group associated with a first location, wherein thecontext-sharing group is a collection of at least two electronic devicesthat each share context information with at least one other electronicdevice included in the collection, and wherein the collection includesat least a second electronic device and a context collector: receiving auser voice input; receiving, from the context collector, an aggregatecontext of the context-sharing group; after receiving the aggregatecontext, providing at least a portion of the aggregate context and datacorresponding to the user voice input to a remote device that is notparticipating in the context-sharing group; receiving, from the remotedevice, a command to perform one or more tasks and a device identifiercorresponding to the second electronic device, wherein the remote devicedetermines the one or more tasks and the device identifier based on thedata corresponding to the user voice input and context informationincluded in the at least a portion of the aggregate context; andtransmitting the command to the second electronic device based on thedevice identifier, wherein the command causes the second electronicdevice to perform the one or more tasks.

An example system comprises one or more processors; memory; and one ormore programs, where the one or more programs are stored in the memoryand are configured to be executed by the one or more processors, the oneor more programs including instructions for: receiving a user voiceinput and at least a portion of an aggregate context of acontext-sharing group associated with a first location from a firstelectronic device that is participating in the context-sharing group,wherein the context-sharing group is a collection of a plurality ofelectronic devices that each share context information with at least oneother electronic device included in the collection; determining a userintent based on the user voice input; determining one or more taskscorresponding to the user intent; identifying a second electronic deviceof the plurality of electronic devices to perform the one or more tasksbased on the one or more tasks and context information included in theat least a portion of the aggregate context; and transmitting, to thefirst electronic device, a command to perform the one or more tasks anda device identifier corresponding to the second electronic device,wherein the first electronic transmits the command to the secondelectronic device based on the device identifier, and wherein thecommand causes the second electronic device to perform the one or moretasks.

Another example first electronic device comprises one or moreprocessors; a memory; and one or more programs, where the one or moreprograms are stored in the memory and are configured to be executed bythe one or more processors, the one or more programs includinginstructions for: while the first electronic device is participating ina context-sharing group associated with a first location, wherein thecontext-sharing group is a collection of a plurality of electronicdevices that each share context information with at least one otherelectronic device included in the collection, and wherein the collectionincludes a context collector: receiving a user voice input; receiving,from the context collector, an aggregate context of the context-sharinggroup; after receiving the aggregate context, providing at least aportion of the aggregate context and data corresponding to the uservoice input to a remote device that is not participating in thecontext-sharing group, wherein the remote device determines a pluralityof tasks based on the data corresponding to the user voice input;receiving, from the remote device: a first command to perform a firstset of tasks of the plurality of tasks and a second command to perform asecond set of tasks of the plurality of tasks; and a first deviceidentifier corresponding to a second electronic device of the pluralityof electronic devices and a second device identifier corresponding to athird electronic device of the plurality of electronic devices;transmitting the first command to the second electronic device based onthe first device identifier, wherein the first command causes the secondelectronic device to perform the first set of tasks; and transmittingthe second command to the third electronic device based on the seconddevice identifier, wherein the second command causes the thirdelectronic device to perform the second set of tasks.

Another example system comprises one or more processors; memory; and oneor more programs, where the one or more programs are stored in thememory and are configured to be executed by the one or more processors,the one or more programs including instructions for: while a firstelectronic device and a second electronic device are participating in acontext-sharing group associated with a first location, wherein thecontext-sharing group is a collection of at least two electronic devicesthat each share context information with at least one other electronicdevice included in the collection, and wherein the collection includes acontext collector: receiving, at the first electronic device, a firstuser voice input; outputting, at the first electronic device, a firstdigital assistant response based on the first user voice input, whereinthe first electronic device transmits context information including adigital assistant dialog session history for the first electronic deviceto the context collector after outputting the first digital assistantresponse; receiving, at the second electronic device, a second uservoice input; receiving, at the second electronic device, an updatedaggregate context of the context-sharing group from the contextcollector, wherein the updated aggregate context includes the digitalassistant dialog session history for the first electronic device; andoutputting, at the second electronic device, a second digital assistantresponse based on the second user voice input and the digital assistantdialog history for the first electronic device.

Another example first electronic device comprises one or moreprocessors; a memory; and one or more programs, where the one or moreprograms are stored in the memory and are configured to be executed bythe one or more processors, the one or more programs includinginstructions for: while the first electronic device is participating ina context-sharing group associated with a first location, wherein thecontext-sharing group is a collection of at least two electronic devicesthat each share context information with at least one other electronicdevice participating in the collection, and wherein the collectionincludes at least a second electronic device and a context collector:receiving a user voice input, wherein the user voice input includes adigital assistant trigger; in response to detecting the digitalassistant trigger, transmitting a first trigger advertisement to thecontext collector, wherein the first trigger advertisement indicates afirst time at which the digital assistant trigger ended according to thefirst electronic device; receiving, from the context collector, a secondtrigger advertisement, wherein the second trigger advertisementindicates a second time at which the digital assistant trigger endedaccording to the second electronic device; determining whether thesecond time is within a predetermined time range before the first time;and in accordance with a determination that the second time is withinthe predetermined time range before the first time, forgoing furtherprocessing of the user voice input.

An example first electronic device comprises means for joining acontext-sharing group associated with a first location, wherein thecontext-sharing group is a collection of at least two electronic devicesthat each share context information with at least one other electronicdevice included in the collection, and wherein the collection includesat least a second electronic device. After joining the context-sharinggroup, means for electing one electronic device of the collection of atleast two electronic devices as a context collector of thecontext-sharing group, wherein electing the context collector includes:determining a first context collector score corresponding to the firstelectronic device based at least on a strength of connectivity betweenthe first electronic device and a wireless network of the firstlocation; receiving, from at least the second electronic device, one ormore context collector scores corresponding to at least the secondelectronic device; and determining, based on the first context collectorscore and the one or more context collector scores corresponding to atleast the second electronic device, which electronic device of theelectronic devices included in the context-sharing group to elect as thecontext collector of the context-sharing group. In accordance with adetermination to elect the first electronic device as the contextcollector, means for receiving context information from at least thesecond electronic device in response to at least the second electronicdevice undergoing a device state change.

Another example first electronic device comprises means for: while thefirst electronic device is participating in a context-sharing groupassociated with a first location, wherein the context-sharing group is acollection of at least two electronic devices that each share contextinformation with at least one other electronic device included in thecollection, and wherein the collection includes at least a secondelectronic device and a context collector: receiving a user voice input;means for receiving, from the context collector, an aggregate context ofthe context-sharing group; after receiving the aggregate context, meansfor providing at least a portion of the aggregate context and datacorresponding to the user voice input to a remote device that is notparticipating in the context-sharing group; means for receiving, fromthe remote device, a command to perform one or more tasks and a deviceidentifier corresponding to the second electronic device, wherein theremote device determines the one or more tasks and the device identifierbased on the data corresponding to the user voice input and contextinformation included in the at least a portion of the aggregate context;and means for transmitting the command to the second electronic devicebased on the device identifier, wherein the command causes the secondelectronic device to perform the one or more tasks.

Another example system comprises means for: receiving a user voice inputand at least a portion of an aggregate context of a context-sharinggroup associated with a first location from a first electronic devicethat is participating in the context-sharing group, wherein thecontext-sharing group is a collection of a plurality of electronicdevices that each share context information with at least one otherelectronic device included in the collection; means for determining auser intent based on the user voice input; means for determining one ormore tasks corresponding to the user intent; means for identifying asecond electronic device of the plurality of electronic devices toperform the one or more tasks based on the one or more tasks and contextinformation included in the at least a portion of the aggregate context;and means for transmitting, to the first electronic device, a command toperform the one or more tasks and a device identifier corresponding tothe second electronic device, wherein the first electronic transmits thecommand to the second electronic device based on the device identifier,and wherein the command causes the second electronic device to performthe one or more tasks.

Another example first electronic device comprises means for: while thefirst electronic device is participating in a context-sharing groupassociated with a first location, wherein the context-sharing group is acollection of a plurality of electronic devices that each share contextinformation with at least one other electronic device included in thecollection, and wherein the collection includes a context collector:receiving a user voice input; means for receiving, from the contextcollector, an aggregate context of the context-sharing group; afterreceiving the aggregate context, means for providing at least a portionof the aggregate context and data corresponding to the user voice inputto a remote device that is not participating in the context-sharinggroup, wherein the remote device determines a plurality of tasks basedon the data corresponding to the user voice input; means for receiving,from the remote device: a first command to perform a first set of tasksof the plurality of tasks and a second command to perform a second setof tasks of the plurality of tasks; and a first device identifiercorresponding to a second electronic device of the plurality ofelectronic devices and a second device identifier corresponding to athird electronic device of the plurality of electronic devices; meansfor transmitting the first command to the second electronic device basedon the first device identifier, wherein the first command causes thesecond electronic device to perform the first set of tasks; and meansfor transmitting the second command to the third electronic device basedon the second device identifier, wherein the second command causes thethird electronic device to perform the second set of tasks.

Another example system comprises means for: while a first electronicdevice and a second electronic device are participating in acontext-sharing group associated with a first location, wherein thecontext-sharing group is a collection of at least two electronic devicesthat each share context information with at least one other electronicdevice included in the collection, and wherein the collection includes acontext collector: receiving, at the first electronic device, a firstuser voice input; means for outputting, at the first electronic device,a first digital assistant response based on the first user voice input,wherein the first electronic device transmits context informationincluding a digital assistant dialog session history for the firstelectronic device to the context collector after outputting the firstdigital assistant response; means for receiving, at the secondelectronic device, a second user voice input; means for receiving, atthe second electronic device, an updated aggregate context of thecontext-sharing group from the context collector, wherein the updatedaggregate context includes the digital assistant dialog session historyfor the first electronic device; and means for outputting, at the secondelectronic device, a second digital assistant response based on thesecond user voice input and the digital assistant dialog history for thefirst electronic device.

Another example first electronic device comprises means for: while thefirst electronic device is participating in a context-sharing groupassociated with a first location, wherein the context-sharing group is acollection of at least two electronic devices that each share contextinformation with at least one other electronic device participating inthe collection, and wherein the collection includes at least a secondelectronic device and a context collector: receiving a user voice input,wherein the user voice input includes a digital assistant trigger; inresponse to detecting the digital assistant trigger, transmitting afirst trigger advertisement to the context collector, wherein the firsttrigger advertisement indicates a first time at which the digitalassistant trigger ended according to the first electronic device;receiving, from the context collector, a second trigger advertisement,wherein the second trigger advertisement indicates a second time atwhich the digital assistant trigger ended according to the secondelectronic device; determining whether the second time is within apredetermined time range before the first time; and in accordance with adetermination that the second time is within the predetermined timerange before the first time, forgoing further processing of the uservoice input.

In some examples, determining a first context collector scorecorresponding to a first electronic device based at least on a strengthof connectivity between the first electronic device and a wirelessnetwork of the first location, and subsequently determining, based onthe first context collector score and one or more context collectorscores corresponding to at least a second electronic device, whichelectronic device of the electronic devices included in acontext-sharing group to elect as the context collector of thecontext-sharing group, may improve a user's digital assistantexperience. Specifically, determining the first context collector scoresbased at least on a strength of connectivity between the firstelectronic device and the wireless network of the first location helpsensure that an electronic device that has a strong connection to thewireless network will be elected as the context collector, as thecontext collector election is based on determined context collectorscores. This in turn improves the stability of the context collectorbecause the context collector is much less likely to lose its connectionto the wireless network and leave the context-sharing group. In thismanner, the collector will be able to consistently receive and transmitcontext information to electronic devices participating in thecontext-sharing group, which will allow the digital assistants of theelectronic devices to respond to user requests based on the contextinformation provided to and received from the context collector.

In some examples, providing at least a portion of an aggregate contextand data corresponding to a user voice input to a remote device that isnot participating in a context-sharing group so that the remote devicemay determine one or more tasks and a device identifier based on thedata corresponding to the user voice input and context informationincluded in at least a portion of the aggregate context, may improve auser's digital assistant experience. Specifically, by performing theabove, the remote device is able to, for example, more accuratelydetermine a user intent corresponding to the user voice input, as thecontext information included in the aggregate context informs the remotedevice of a user's context when providing the user voice input withrespect to all of the devices participating in a context-sharing groupinstead of only the first electronic device that receives the user voiceinput. This in turn allows the remote device to determine an optimalelectronic device for responding to the user based on the one or moretasks corresponding to the determined user intent and the contextinformation included in the aggregate context. Thus, even if the firstelectronic device receives the user voice input, the first electronicdevice may transmit the one or more tasks to another electronic devicethat is more suitable for performing the one or more tasks (e.g., moreclosely positioned to the user, better device capabilities forperforming the one or more tasks, etc.) based on the device identifierprovided by the remote device. Thus, the first electronic device'sprovision of the aggregate context to the remote device, as well as thefirst electronic device's transmission of the one or more tasks to asecond electronic device based on the received device identifier, allowsthe digital assistants of the electronic devices participating in acontext-sharing group to intelligently coordinate the performance oftasks among one another, which creates an appearance of a single digitalassistant that is interacting with the user across the multiple devicesinstead of multiple individual digital assistants at each of themultiple device.

In some examples, identifying a second electronic device of a pluralityof electronic devices participating in a context-sharing group toperform one or more tasks based on the one or more tasks and contextinformation included in at least a portion of an aggregate context ofthe context-sharing group, may improve a user's digital assistantexperience. Specifically, as mentioned above, an electronic device thatreceives a user's digital assistant request may not be the most optimaldevice for performing the requested tasks. For example, the electronicdevice that receives a user's request may not be the most optimal devicebecause the device may have a small display (or no display at all), therequest may be directed to an event (e.g., an alarm, a timer, mediaplayback, etc.) occurring at another electronic device, and/or there maybe another electronic device that is more conveniently positionedrelative to the user. Thus, because the aggregate context includescontext information (associated with multiple devices participating inthe context-sharing group) that indicates, for example, devicecapabilities, device position, and current and/or previous deviceactivities and user interactions, a remote device (e.g., one or moreservers) may identify a second, more suitable electronic device forperforming the one or more tasks based on the context informationinstead of simply instructing the electronic device that receives theuser's request to perform the one or more tasks. This in turn improvesthe user's digital assistant experience, as it creates an appearance ofa single digital assistant that is intelligently interacting with theuser across multiple devices in order to provide an optimal response tothe user's request.

Transmitting a first command to perform a first set of tasks of aplurality of tasks to a second electronic device and transmitting asecond command to perform a second set of tasks of the plurality oftasks to a third electronic device, may improve a user's digitalassistant experience. Specifically, when a user's digital assistantrequest requires the performance of a plurality of tasks such as, forexample, the output of a digital assistant response and the display ofcorresponding data/information, assigning the performance of certaintasks to different devices helps ensure that those tasks are beingperformed by optimal devices. For example, while the second electronicdevice may have suitable audio capabilities for providing a digitalassistant response, it may have a small display (or no display at all).Thus, instead of displaying data/information on a small display (or notdisplaying it at all), the second electronic device may be instructed toprovide an audio digital assistant response via the first command whilethe third electronic device (e.g., that has a larger display than thesecond electronic device) may be instructed to display the correspondingdata/information. This in turn improves the user's digital assistantexperience, as it creates an appearance of a single digital assistantthat is intelligently interacting with the user across multiple devicesin order to provide an optimal response to the user's request.

In some examples, outputting, at a second electronic device, a seconddigital assistant response based on a second user voice input and adigital assistant dialog history for a first electronic device mayimprove a user's digital assistant experience. Specifically, using adigital assistant dialog history for a first electronic device todetermine the second digital assistant response allows a digitalassistant of the second electronic device to provide a digital assistantresponse that is based on, and/or is in furtherance to, a first userinput even though the first user input was provided to the firstelectronic device instead of the second electronic device. In thismanner, a user of the second electronic device may provide a digitalassistant request (e.g., in the second user input) in a more natural andconversational manner, and without having to repeat certain aspects of arequest if those aspects were already introduced in the first userinput. For example, if the first user voice input includes the userrequest “Hey Siri, what's the weather like in Palo Alto?”, a user of thesecond electronic device can subsequently request weather informationwith respect to New York by providing the second user voice input “HeySiri, how about in New York?” instead of having to repeat that weatherinformation is desired (e.g., “Hey Siri, what's the weather like in NewYork?”). This in turn improves the user's digital assistant experience,as it creates an appearance of a single digital assistant that isinteracting with the user across multiple devices instead of multipleindividual digital assistants at each of the multiple devices.

In some examples, determining whether a second time at which a digitalassistant trigger included in a user voice input ended according to asecond electronic device is within a predetermined time range before afirst time at which the digital assistant trigger ended according to afirst electronic device, and forgoing further processing of the uservoice input in accordance with a determination that the second time iswithin the predetermined time range before the first time, may improve auser's digital assistant experience. Specifically, if an electronicdevice's digital assistant trigger detection is delayed, the electronicdevice will begin processing a user voice input even if another nearbyelectronic device (that did not have a delayed digital assistant triggerdetection) has already begun processing the user voice input and/or hasalready provided a response to the user voice input. This in turn mayresult in multiple devices providing a response to the same user voiceinput at different times, which may result in a poor digital assistantexperience for the user (e.g., due to user confusion and/or annoyance).Accordingly, forgoing further processing of a user voice input if anelectronic device determines that another electronic device has alreadydetected a digital assistant trigger (within a predetermined time range)will ensure that multiple devices do not provide a response to the sameuser voice input at different times, which in turn will improve a user'sdigital assistant experience.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a system and environment forimplementing a digital assistant, according to various examples.

FIG. 2A is a block diagram illustrating a portable multifunction deviceimplementing the client-side portion of a digital assistant, accordingto various examples.

FIG. 2B is a block diagram illustrating exemplary components for eventhandling, according to various examples.

FIG. 3 illustrates a portable multifunction device implementing theclient-side portion of a digital assistant, according to variousexamples.

FIG. 4 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface, according to various examples.

FIG. 5A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device, according to variousexamples.

FIG. 5B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the display,according to various examples.

FIG. 6A illustrates a personal electronic device, according to variousexamples.

FIG. 6B is a block diagram illustrating a personal electronic device,according to various examples.

FIG. 7A is a block diagram illustrating a digital assistant system or aserver portion thereof, according to various examples.

FIG. 7B illustrates the functions of the digital assistant shown in FIG.7A, according to various examples.

FIG. 7C illustrates a portion of an ontology, according to variousexamples.

FIG. 8 illustrates a system and technique for electing a contextcollector of a context-sharing group, according to various examples.

FIG. 9 illustrates a system and technique for performing one or moretasks in a context-sharing group, according to various examples.

FIG. 10 illustrates a system and technique for suppressing a delayeddigital assistant trigger detection using a context collector of acontext-sharing group, according to various examples.

FIG. 11 is a block diagram illustrating a system for task determinationand device selection in a context-sharing group, according to variousexamples.

FIGS. 12A-12B illustrate a system and technique for multimodal taskperformance in a context-sharing group, according to various examples.

FIG. 13 illustrates a system and technique for continuous digitalassistant conversations across multiple devices participating in acontext-sharing group, according to various examples.

FIGS. 14A-14C illustrate a flow chart representing a process forelecting a context collector of a context-sharing group, according tovarious examples.

FIGS. 15A-15B illustrate a flow chart representing a process forperforming one or more tasks in a context-sharing group, according tovarious examples.

FIGS. 16A-16E illustrate a flow chart representing a process foridentifying an electronic device participating in a context-sharinggroup to perform one or more tasks, according to various examples.

FIGS. 17A-17C illustrate a flow chart representing a process formultimodal task performance in a context-sharing group, according tovarious examples.

FIGS. 18A-18B illustrate a flow chart representing a process for acontinuous digital assistant conversation across multiple electronicdevices participating in a context-sharing group, according to variousexamples.

FIGS. 19A-19B illustrate a flow chart representing a process forsuppressing a delayed digital assistant trigger detection using acontext collector of a context-sharing group, according to variousexamples.

DETAILED DESCRIPTION

In the following description of examples, reference is made to theaccompanying drawings in which are shown by way of illustration specificexamples that can be practiced. It is to be understood that otherexamples can be used and structural changes can be made withoutdeparting from the scope of the various examples.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first input could be termed a second input, and,similarly, a second input could be termed a first input, withoutdeparting from the scope of the various described examples. The firstinput and the second input are both inputs and, in some cases, areseparate and different inputs.

The terminology used in the description of the various describedexamples herein is for the purpose of describing particular examplesonly and is not intended to be limiting. As used in the description ofthe various described examples and the appended claims, the singularforms “a,” “an,” and “the” are intended to include the plural forms aswell, unless the context clearly indicates otherwise. It will also beunderstood that the term “and/or” as used herein refers to andencompasses any and all possible combinations of one or more of theassociated listed items. It will be further understood that the terms“includes,” “including,” “comprises,” and/or “comprising,” when used inthis specification, specify the presence of stated features, integers,steps, operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

1. System and Environment

FIG. 1 illustrates a block diagram of system 100 according to variousexamples. In some examples, system 100 implements a digital assistant.The terms “digital assistant,” “virtual assistant,” “intelligentautomated assistant,” or “automatic digital assistant” refer to anyinformation processing system that interprets natural language input inspoken and/or textual form to infer user intent, and performs actionsbased on the inferred user intent. For example, to act on an inferreduser intent, the system performs one or more of the following:identifying a task flow with steps and parameters designed to accomplishthe inferred user intent, inputting specific requirements from theinferred user intent into the task flow; executing the task flow byinvoking programs, methods, services, APIs, or the like; and generatingoutput responses to the user in an audible (e.g., speech) and/or visualform.

Specifically, a digital assistant is capable of accepting a user requestat least partially in the form of a natural language command, request,statement, narrative, and/or inquiry. Typically, the user request seekseither an informational answer or performance of a task by the digitalassistant. A satisfactory response to the user request includes aprovision of the requested informational answer, a performance of therequested task, or a combination of the two. For example, a user asksthe digital assistant a question, such as “Where am I right now?” Basedon the user's current location, the digital assistant answers, “You arein Central Park near the west gate.” The user also requests theperformance of a task, for example, “Please invite my friends to mygirlfriend's birthday party next week.” In response, the digitalassistant can acknowledge the request by saying “Yes, right away,” andthen send a suitable calendar invite on behalf of the user to each ofthe user's friends listed in the user's electronic address book. Duringperformance of a requested task, the digital assistant sometimesinteracts with the user in a continuous dialogue involving multipleexchanges of information over an extended period of time. There arenumerous other ways of interacting with a digital assistant to requestinformation or performance of various tasks. In addition to providingverbal responses and taking programmed actions, the digital assistantalso provides responses in other visual or audio forms, e.g., as text,alerts, music, videos, animations, etc.

As shown in FIG. 1, in some examples, a digital assistant is implementedaccording to a client-server model. The digital assistant includesclient-side portion 102 (hereafter “DA client 102”) executed on userdevice 104 and server-side portion 106 (hereafter “DA server 106”)executed on server system 108. DA client 102 communicates with DA server106 through one or more networks 110. DA client 102 provides client-sidefunctionalities such as user-facing input and output processing andcommunication with DA server 106. DA server 106 provides server-sidefunctionalities for any number of DA clients 102 each residing on arespective user device 104.

In some examples, DA server 106 includes client-facing I/O interface112, one or more processing modules 114, data and models 116, and I/Ointerface to external services 118. The client-facing I/O interface 112facilitates the client-facing input and output processing for DA server106. One or more processing modules 114 utilize data and models 116 toprocess speech input and determine the user's intent based on naturallanguage input. Further, one or more processing modules 114 perform taskexecution based on inferred user intent. In some examples, DA server 106communicates with external services 120 through network(s) 110 for taskcompletion or information acquisition. I/O interface to externalservices 118 facilitates such communications.

User device 104 can be any suitable electronic device. In some examples,user device 104 is a portable multifunctional device (e.g., device 200,described below with reference to FIG. 2A), a multifunctional device(e.g., device 400, described below with reference to FIG. 4), or apersonal electronic device (e.g., device 600, described below withreference to FIGS. 6A-6B.) A portable multifunctional device is, forexample, a mobile telephone that also contains other functions, such asPDA and/or music player functions. Specific examples of portablemultifunction devices include the Apple Watch®, iPhone®, iPod Touch®,and iPad® devices from Apple Inc. of Cupertino, Calif. Other examples ofportable multifunction devices include, without limitation,earphones/headphones, speakers, and laptop or tablet computers. Further,in some examples, user device 104 is a non-portable multifunctionaldevice. In particular, user device 104 is a desktop computer, a gameconsole, a speaker, a television, or a television set-top box. In someexamples, user device 104 includes a touch-sensitive surface (e.g.,touch screen displays and/or touchpads). Further, user device 104optionally includes one or more other physical user-interface devices,such as a physical keyboard, a mouse, and/or a joystick. Variousexamples of electronic devices, such as multifunctional devices, aredescribed below in greater detail.

Examples of communication network(s) 110 include local area networks(LAN) and wide area networks (WAN), e.g., the Internet. Communicationnetwork(s) 110 is implemented using any known network protocol,including various wired or wireless protocols, such as, for example,Ethernet, Universal Serial Bus (USB), FIREWIRE, Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), codedivision multiple access (CDMA), time division multiple access (TDMA),Bluetooth, Wi-Fi, voice over Internet Protocol (VoIP), Wi-MAX, or anyother suitable communication protocol.

Server system 108 is implemented on one or more standalone dataprocessing apparatus or a distributed network of computers. In someexamples, server system 108 also employs various virtual devices and/orservices of third-party service providers (e.g., third-party cloudservice providers) to provide the underlying computing resources and/orinfrastructure resources of server system 108.

In some examples, user device 104 communicates with DA server 106 viasecond user device 122. Second user device 122 is similar or identicalto user device 104. For example, second user device 122 is similar todevices 200, 400, or 600 described below with reference to FIGS. 2A, 4,and 6A-6B. User device 104 is configured to communicatively couple tosecond user device 122 via a direct communication connection, such asBluetooth, NFC, BTLE, or the like, or via a wired or wireless network,such as a local Wi-Fi network. In some examples, second user device 122is configured to act as a proxy between user device 104 and DA server106. For example, DA client 102 of user device 104 is configured totransmit information (e.g., a user request received at user device 104)to DA server 106 via second user device 122. DA server 106 processes theinformation and returns relevant data (e.g., data content responsive tothe user request) to user device 104 via second user device 122.

In some examples, user device 104 is configured to communicateabbreviated requests for data to second user device 122 to reduce theamount of information transmitted from user device 104. Second userdevice 122 is configured to determine supplemental information to add tothe abbreviated request to generate a complete request to transmit to DAserver 106. This system architecture can advantageously allow userdevice 104 having limited communication capabilities and/or limitedbattery power (e.g., a watch or a similar compact electronic device) toaccess services provided by DA server 106 by using second user device122, having greater communication capabilities and/or battery power(e.g., a mobile phone, laptop computer, tablet computer, or the like),as a proxy to DA server 106. While only two user devices 104 and 122 areshown in FIG. 1, it should be appreciated that system 100, in someexamples, includes any number and type of user devices configured inthis proxy configuration to communicate with DA server system 106.

Although the digital assistant shown in FIG. 1 includes both aclient-side portion (e.g., DA client 102) and a server-side portion(e.g., DA server 106), in some examples, the functions of a digitalassistant are implemented as a standalone application installed on auser device. In addition, the divisions of functionalities between theclient and server portions of the digital assistant can vary indifferent implementations. For instance, in some examples, the DA clientis a thin-client that provides only user-facing input and outputprocessing functions, and delegates all other functionalities of thedigital assistant to a backend server.

2. Electronic Devices

Attention is now directed toward embodiments of electronic devices forimplementing the client-side portion of a digital assistant. FIG. 2A isa block diagram illustrating portable multifunction device 200 withtouch-sensitive display system 212 in accordance with some embodiments.Touch-sensitive display 212 is sometimes called a “touch screen” forconvenience and is sometimes known as or called a “touch-sensitivedisplay system.” Device 200 includes memory 202 (which optionallyincludes one or more computer-readable storage mediums), memorycontroller 222, one or more processing units (CPUs) 220, peripheralsinterface 218, RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, input/output (I/O) subsystem 206, other input controldevices 216, and external port 224. Device 200 optionally includes oneor more optical sensors 264. Device 200 optionally includes one or morecontact intensity sensors 265 for detecting intensity of contacts ondevice 200 (e.g., a touch-sensitive surface such as touch-sensitivedisplay system 212 of device 200). Device 200 optionally includes one ormore tactile output generators 267 for generating tactile outputs ondevice 200 (e.g., generating tactile outputs on a touch-sensitivesurface such as touch-sensitive display system 212 of device 200 ortouchpad 455 of device 400). These components optionally communicateover one or more communication buses or signal lines 203.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 200 is only one example of aportable multifunction device, and that device 200 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 2A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 202 includes one or more computer-readable storage mediums. Thecomputer-readable storage mediums are, for example, tangible andnon-transitory. Memory 202 includes high-speed random access memory andalso includes non-volatile memory, such as one or more magnetic diskstorage devices, flash memory devices, or other non-volatile solid-statememory devices. Memory controller 222 controls access to memory 202 byother components of device 200.

In some examples, a non-transitory computer-readable storage medium ofmemory 202 is used to store instructions (e.g., for performing aspectsof processes described below) for use by or in connection with aninstruction execution system, apparatus, or device, such as acomputer-based system, processor-containing system, or other system thatcan fetch the instructions from the instruction execution system,apparatus, or device and execute the instructions. In other examples,the instructions (e.g., for performing aspects of the processesdescribed below) are stored on a non-transitory computer-readablestorage medium (not shown) of the server system 108 or are dividedbetween the non-transitory computer-readable storage medium of memory202 and the non-transitory computer-readable storage medium of serversystem 108.

Peripherals interface 218 is used to couple input and output peripheralsof the device to CPU 220 and memory 202. The one or more processors 220run or execute various software programs and/or sets of instructionsstored in memory 202 to perform various functions for device 200 and toprocess data. In some embodiments, peripherals interface 218, CPU 220,and memory controller 222 are implemented on a single chip, such as chip204. In some other embodiments, they are implemented on separate chips.

RF (radio frequency) circuitry 208 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 208 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 208 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 208 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 208optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 210, speaker 211, and microphone 213 provide an audiointerface between a user and device 200. Audio circuitry 210 receivesaudio data from peripherals interface 218, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 211.Speaker 211 converts the electrical signal to human-audible sound waves.Audio circuitry 210 also receives electrical signals converted bymicrophone 213 from sound waves. Audio circuitry 210 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 218 for processing. Audio data are retrieved fromand/or transmitted to memory 202 and/or RF circuitry 208 by peripheralsinterface 218. In some embodiments, audio circuitry 210 also includes aheadset jack (e.g., 312, FIG. 3). The headset jack provides an interfacebetween audio circuitry 210 and removable audio input/outputperipherals, such as output-only headphones or a headset with bothoutput (e.g., a headphone for one or both ears) and input (e.g., amicrophone).

I/O subsystem 206 couples input/output peripherals on device 200, suchas touch screen 212 and other input control devices 216, to peripheralsinterface 218. I/O subsystem 206 optionally includes display controller256, optical sensor controller 258, intensity sensor controller 259,haptic feedback controller 261, and one or more input controllers 260for other input or control devices. The one or more input controllers260 receive/send electrical signals from/to other input control devices216. The other input control devices 216 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 260 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 308, FIG.3) optionally include an up/down button for volume control of speaker211 and/or microphone 213. The one or more buttons optionally include apush button (e.g., 306, FIG. 3).

A quick press of the push button disengages a lock of touch screen 212or begin a process that uses gestures on the touch screen to unlock thedevice, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 306)turns power to device 200 on or off. The user is able to customize afunctionality of one or more of the buttons. Touch screen 212 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 212 provides an input interface and an outputinterface between the device and a user. Display controller 256 receivesand/or sends electrical signals from/to touch screen 212. Touch screen212 displays visual output to the user. The visual output includesgraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput correspond to user-interface objects.

Touch screen 212 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 212 and display controller 256 (along with anyassociated modules and/or sets of instructions in memory 202) detectcontact (and any movement or breaking of the contact) on touch screen212 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 212. In an exemplaryembodiment, a point of contact between touch screen 212 and the usercorresponds to a finger of the user.

Touch screen 212 uses LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 212 and display controller 256 detectcontact and any movement or breaking thereof using any of a plurality oftouch sensing technologies now known or later developed, including butnot limited to capacitive, resistive, infrared, and surface acousticwave technologies, as well as other proximity sensor arrays or otherelements for determining one or more points of contact with touch screen212. In an exemplary embodiment, projected mutual capacitance sensingtechnology is used, such as that found in the iPhone® and iPod Touch®from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 212 isanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), 6,570,557(Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. PatentPublication 2002/0015024A1, each of which is hereby incorporated byreference in its entirety. However, touch screen 212 displays visualoutput from device 200, whereas touch-sensitive touchpads do not providevisual output.

A touch-sensitive display in some embodiments of touch screen 212 is asdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 212 has, for example, a video resolution in excess of 100dpi. In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user makes contact with touch screen 212using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 200includes a touchpad (not shown) for activating or deactivatingparticular functions. In some embodiments, the touchpad is atouch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is a touch-sensitive surfacethat is separate from touch screen 212 or an extension of thetouch-sensitive surface formed by the touch screen.

Device 200 also includes power system 262 for powering the variouscomponents. Power system 262 includes a power management system, one ormore power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 200 also includes one or more optical sensors 264. FIG. 2A showsan optical sensor coupled to optical sensor controller 258 in I/Osubsystem 206. Optical sensor 264 includes charge-coupled device (CCD)or complementary metal-oxide semiconductor (CMOS) phototransistors.Optical sensor 264 receives light from the environment, projectedthrough one or more lenses, and converts the light to data representingan image. In conjunction with imaging module 243 (also called a cameramodule), optical sensor 264 captures still images or video. In someembodiments, an optical sensor is located on the back of device 200,opposite touch screen display 212 on the front of the device so that thetouch screen display is used as a viewfinder for still and/or videoimage acquisition. In some embodiments, an optical sensor is located onthe front of the device so that the user's image is obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 264 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 264 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 200 optionally also includes one or more contact intensitysensors 265. FIG. 2A shows a contact intensity sensor coupled tointensity sensor controller 259 in I/O subsystem 206. Contact intensitysensor 265 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 265 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 212). In some embodiments, at least one contact intensitysensor is located on the back of device 200, opposite touch screendisplay 212, which is located on the front of device 200.

Device 200 also includes one or more proximity sensors 266. FIG. 2Ashows proximity sensor 266 coupled to peripherals interface 218.Alternately, proximity sensor 266 is coupled to input controller 260 inI/O subsystem 206. Proximity sensor 266 is performed as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 212 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 200 optionally also includes one or more tactile outputgenerators 267. FIG. 2A shows a tactile output generator coupled tohaptic feedback controller 261 in I/O subsystem 206. Tactile outputgenerator 267 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 265 receives tactile feedbackgeneration instructions from haptic feedback module 233 and generatestactile outputs on device 200 that are capable of being sensed by a userof device 200. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 212) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 200) or laterally (e.g., back and forth inthe same plane as a surface of device 200). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 200, opposite touch screen display 212, which is located on thefront of device 200.

Device 200 also includes one or more accelerometers 268. FIG. 2A showsaccelerometer 268 coupled to peripherals interface 218. Alternately,accelerometer 268 is coupled to an input controller 260 in I/O subsystem206. Accelerometer 268 performs, for example, as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 200 optionally includes, in addition to accelerometer(s) 268, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 200.

In some embodiments, the software components stored in memory 202include operating system 226, communication module (or set ofinstructions) 228, contact/motion module (or set of instructions) 230,graphics module (or set of instructions) 232, text input module (or setof instructions) 234, Global Positioning System (GPS) module (or set ofinstructions) 235, Digital Assistant Client Module 229, and applications(or sets of instructions) 236. Further, memory 202 stores data andmodels, such as user data and models 231.

Furthermore, in some embodiments, memory 202 (FIG. 2A) or 470 (FIG. 4)stores device/global internal state 257, as shown in FIGS. 2A and 4.Device/global internal state 257 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 212; sensorstate, including information obtained from the device's various sensorsand input control devices 216; and location information concerning thedevice's location and/or attitude.

Operating system 226 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 228 facilitates communication with other devicesover one or more external ports 224 and also includes various softwarecomponents for handling data received by RF circuitry 208 and/orexternal port 224. External port 224 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 230 optionally detects contact with touch screen212 (in conjunction with display controller 256) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 230 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 230 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 230 and display controller 256 detect contact on atouchpad.

In some embodiments, contact/motion module 230 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 200). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 230 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 232 includes various known software components forrendering and displaying graphics on touch screen 212 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 232 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 232 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 256.

Haptic feedback module 233 includes various software components forgenerating instructions used by tactile output generator(s) 267 toproduce tactile outputs at one or more locations on device 200 inresponse to user interactions with device 200.

Text input module 234, which is, in some examples, a component ofgraphics module 232, provides soft keyboards for entering text invarious applications (e.g., contacts 237, email 240, IM 241, browser247, and any other application that needs text input).

GPS module 235 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 238 foruse in location-based dialing; to camera 243 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Digital assistant client module 229 includes various client-side digitalassistant instructions to provide the client-side functionalities of thedigital assistant. For example, digital assistant client module 229 iscapable of accepting voice input (e.g., speech input), text input, touchinput, and/or gestural input through various user interfaces (e.g.,microphone 213, accelerometer(s) 268, touch-sensitive display system212, optical sensor(s) 264, other input control devices 216, etc.) ofportable multifunction device 200. Digital assistant client module 229is also capable of providing output in audio (e.g., speech output),visual, and/or tactile forms through various output interfaces (e.g.,speaker 211, touch-sensitive display system 212, tactile outputgenerator(s) 267, etc.) of portable multifunction device 200. Forexample, output is provided as voice, sound, alerts, text messages,menus, graphics, videos, animations, vibrations, and/or combinations oftwo or more of the above. During operation, digital assistant clientmodule 229 communicates with DA server 106 using RF circuitry 208.

User data and models 231 include various data associated with the user(e.g., user-specific vocabulary data, user preference data,user-specified name pronunciations, data from the user's electronicaddress book, to-do lists, shopping lists, etc.) to provide theclient-side functionalities of the digital assistant. Further, user dataand models 231 include various models (e.g., speech recognition models,statistical language models, natural language processing models,ontology, task flow models, service models, etc.) for processing userinput and determining user intent.

In some examples, digital assistant client module 229 utilizes thevarious sensors, subsystems, and peripheral devices of portablemultifunction device 200 to gather additional information from thesurrounding environment of the portable multifunction device 200 toestablish a context associated with a user, the current userinteraction, and/or the current user input. In some examples, digitalassistant client module 229 provides the contextual information or asubset thereof with the user input to DA server 106 to help infer theuser's intent. In some examples, the digital assistant also uses thecontextual information to determine how to prepare and deliver outputsto the user. Contextual information is referred to as context data.

In some examples, the contextual information that accompanies the userinput includes sensor information, e.g., lighting, ambient noise,ambient temperature, images or videos of the surrounding environment,etc. In some examples, the contextual information can also include thephysical state of the device, e.g., device orientation, device location,device temperature, power level, speed, acceleration, motion patterns,cellular signals strength, etc. In some examples, information related tothe software state of DA server 106, e.g., running processes, installedprograms, past and present network activities, background services,error logs, resources usage, etc., and of portable multifunction device200 is provided to DA server 106 as contextual information associatedwith a user input.

In some examples, the digital assistant client module 229 selectivelyprovides information (e.g., user data 231) stored on the portablemultifunction device 200 in response to requests from DA server 106. Insome examples, digital assistant client module 229 also elicitsadditional input from the user via a natural language dialogue or otheruser interfaces upon request by DA server 106. Digital assistant clientmodule 229 passes the additional input to DA server 106 to help DAserver 106 in intent deduction and/or fulfillment of the user's intentexpressed in the user request.

A more detailed description of a digital assistant is described belowwith reference to FIGS. 7A-7C. It should be recognized that digitalassistant client module 229 can include any number of the sub-modules ofdigital assistant module 726 described below.

Applications 236 include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 237 (sometimes called an address book or contact        list);    -   Telephone module 238;    -   Video conference module 239;    -   E-mail client module 240;    -   Instant messaging (IM) module 241;    -   Workout support module 242;    -   Camera module 243 for still and/or video images;    -   Image management module 244;    -   Video player module;    -   Music player module;    -   Browser module 247;    -   Calendar module 248;    -   Widget modules 249, which includes, in some examples, one or        more of: weather widget 249-1, stocks widget 249-2, calculator        widget 249-3, alarm clock widget 249-4, dictionary widget 249-5,        and other widgets obtained by the user, as well as user-created        widgets 249-6;    -   Widget creator module 250 for making user-created widgets 249-6;    -   Search module 251;    -   Video and music player module 252, which merges video player        module and music player module;    -   Notes module 253;    -   Map module 254; and/or    -   Online video module 255.

Examples of other applications 236 that are stored in memory 202 includeother word processing applications, other image editing applications,drawing applications, presentation applications, JAVA-enabledapplications, encryption, digital rights management, voice recognition,and voice replication.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, contacts module 237 are used to manage an address book or contactlist (e.g., stored in application internal state 292 of contacts module237 in memory 202 or memory 470), including: adding name(s) to theaddress book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 238, videoconference module 239, e-mail 240, or IM 241; and so forth.

In conjunction with RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, touch screen 212, display controller 256, contact/motionmodule 230, graphics module 232, and text input module 234, telephonemodule 238 are used to enter a sequence of characters corresponding to atelephone number, access one or more telephone numbers in contactsmodule 237, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication uses any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, touch screen 212, display controller 256, optical sensor264, optical sensor controller 258, contact/motion module 230, graphicsmodule 232, text input module 234, contacts module 237, and telephonemodule 238, video conference module 239 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, e-mail client module 240 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 244,e-mail client module 240 makes it very easy to create and send e-mailswith still or video images taken with camera module 243.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, the instant messaging module 241 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, GPS module 235, map module 254, and music playermodule, workout support module 242 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 212, display controller 256, opticalsensor(s) 264, optical sensor controller 258, contact/motion module 230,graphics module 232, and image management module 244, camera module 243includes executable instructions to capture still images or video(including a video stream) and store them into memory 202, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 202.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, text input module 234,and camera module 243, image management module 244 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, browser module 247 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, e-mail client module 240, and browser module 247,calendar module 248 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, and browser module 247, widget modules 249 aremini-applications that can be downloaded and used by a user (e.g.,weather widget 249-1, stocks widget 249-2, calculator widget 249-3,alarm clock widget 249-4, and dictionary widget 249-5) or created by theuser (e.g., user-created widget 249-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, and browser module 247, the widget creator module 250are used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, search module 251 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 202 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, audio circuitry 210,speaker 211, RF circuitry 208, and browser module 247, video and musicplayer module 252 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 212 or on an external, connected display via externalport 224). In some embodiments, device 200 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, notes module 253 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, GPS module 235, and browser module 247, map module 254are used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions, data on stores and other points ofinterest at or near a particular location, and other location-baseddata) in accordance with user instructions.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, audio circuitry 210,speaker 211, RF circuitry 208, text input module 234, e-mail clientmodule 240, and browser module 247, online video module 255 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 224), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 241, rather than e-mail client module 240, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules can be combined or otherwiserearranged in various embodiments. For example, video player module canbe combined with music player module into a single module (e.g., videoand music player module 252, FIG. 2A). In some embodiments, memory 202stores a subset of the modules and data structures identified above.Furthermore, memory 202 stores additional modules and data structuresnot described above.

In some embodiments, device 200 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device200, the number of physical input control devices (such as push buttons,dials, and the like) on device 200 is reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 200 to a main, home, or root menu from any userinterface that is displayed on device 200. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 2B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 202 (FIG. 2A) or 470 (FIG. 4) includes event sorter 270 (e.g., inoperating system 226) and a respective application 236-1 (e.g., any ofthe aforementioned applications 237-251, 255, 480-490).

Event sorter 270 receives event information and determines theapplication 236-1 and application view 291 of application 236-1 to whichto deliver the event information. Event sorter 270 includes eventmonitor 271 and event dispatcher module 274. In some embodiments,application 236-1 includes application internal state 292, whichindicates the current application view(s) displayed on touch-sensitivedisplay 212 when the application is active or executing. In someembodiments, device/global internal state 257 is used by event sorter270 to determine which application(s) is (are) currently active, andapplication internal state 292 is used by event sorter 270 to determineapplication views 291 to which to deliver event information.

In some embodiments, application internal state 292 includes additionalinformation, such as one or more of: resume information to be used whenapplication 236-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 236-1, a state queue for enabling the user to go back toa prior state or view of application 236-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 271 receives event information from peripherals interface218. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 212, as part of a multi-touchgesture). Peripherals interface 218 transmits information it receivesfrom I/O subsystem 206 or a sensor, such as proximity sensor 266,accelerometer(s) 268, and/or microphone 213 (through audio circuitry210). Information that peripherals interface 218 receives from I/Osubsystem 206 includes information from touch-sensitive display 212 or atouch-sensitive surface.

In some embodiments, event monitor 271 sends requests to the peripheralsinterface 218 at predetermined intervals. In response, peripheralsinterface 218 transmits event information. In other embodiments,peripherals interface 218 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 270 also includes a hit viewdetermination module 272 and/or an active event recognizer determinationmodule 273.

Hit view determination module 272 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 212 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected is called the hit view,and the set of events that are recognized as proper inputs is determinedbased, at least in part, on the hit view of the initial touch thatbegins a touch-based gesture.

Hit view determination module 272 receives information related to subevents of a touch-based gesture. When an application has multiple viewsorganized in a hierarchy, hit view determination module 272 identifies ahit view as the lowest view in the hierarchy which should handle thesub-event. In most circumstances, the hit view is the lowest level viewin which an initiating sub-event occurs (e.g., the first sub-event inthe sequence of sub-events that form an event or potential event). Oncethe hit view is identified by the hit view determination module 272, thehit view typically receives all sub-events related to the same touch orinput source for which it was identified as the hit view.

Active event recognizer determination module 273 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 273 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 273 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 274 dispatches the event information to an eventrecognizer (e.g., event recognizer 280). In embodiments including activeevent recognizer determination module 273, event dispatcher module 274delivers the event information to an event recognizer determined byactive event recognizer determination module 273. In some embodiments,event dispatcher module 274 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 282.

In some embodiments, operating system 226 includes event sorter 270.Alternatively, application 236-1 includes event sorter 270. In yet otherembodiments, event sorter 270 is a stand-alone module, or a part ofanother module stored in memory 202, such as contact/motion module 230.

In some embodiments, application 236-1 includes a plurality of eventhandlers 290 and one or more application views 291, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 291 of the application 236-1 includes one or more event recognizers280. Typically, a respective application view 291 includes a pluralityof event recognizers 280. In other embodiments, one or more of eventrecognizers 280 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 236-1inherits methods and other properties. In some embodiments, a respectiveevent handler 290 includes one or more of: data updater 276, objectupdater 277, GUI updater 278, and/or event data 279 received from eventsorter 270. Event handler 290 utilizes or calls data updater 276, objectupdater 277, or GUI updater 278 to update the application internal state292. Alternatively, one or more of the application views 291 include oneor more respective event handlers 290. Also, in some embodiments, one ormore of data updater 276, object updater 277, and GUI updater 278 areincluded in a respective application view 291.

A respective event recognizer 280 receives event information (e.g.,event data 279) from event sorter 270 and identifies an event from theevent information. Event recognizer 280 includes event receiver 282 andevent comparator 284. In some embodiments, event recognizer 280 alsoincludes at least a subset of: metadata 283, and event deliveryinstructions 288 (which include sub-event delivery instructions).

Event receiver 282 receives event information from event sorter 270. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation also includes speed and direction of the sub-event. In someembodiments, events include rotation of the device from one orientationto another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 284 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 284 includes eventdefinitions 286. Event definitions 286 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(287-1), event 2 (287-2), and others. In some embodiments, sub-events inan event (287) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (287-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (287-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 212, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 290.

In some embodiments, event definition 287 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 284 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 212, when a touch is detected on touch-sensitivedisplay 212, event comparator 284 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 290, the event comparator uses the result of the hit testto determine which event handler 290 should be activated. For example,event comparator 284 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (287) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 280 determines that the series ofsub-events do not match any of the events in event definitions 286, therespective event recognizer 280 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 280 includes metadata283 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 283 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 283 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 280 activates eventhandler 290 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 280 delivers event information associated with theevent to event handler 290. Activating an event handler 290 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 280 throws a flag associated withthe recognized event, and event handler 290 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 288 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 276 creates and updates data used inapplication 236-1. For example, data updater 276 updates the telephonenumber used in contacts module 237, or stores a video file used in videoplayer module. In some embodiments, object updater 277 creates andupdates objects used in application 236-1. For example, object updater277 creates a new user-interface object or updates the position of auser-interface object. GUI updater 278 updates the GUI. For example, GUIupdater 278 prepares display information and sends it to graphics module232 for display on a touch-sensitive display.

In some embodiments, event handler(s) 290 includes or has access to dataupdater 276, object updater 277, and GUI updater 278. In someembodiments, data updater 276, object updater 277, and GUI updater 278are included in a single module of a respective application 236-1 orapplication view 291. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 200 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 3 illustrates a portable multifunction device 200 having a touchscreen 212 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 300.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 302 (not drawn to scalein the figure) or one or more styluses 303 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 200. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 200 also includes one or more physical buttons, such as “home” ormenu button 304. As described previously, menu button 304 is used tonavigate to any application 236 in a set of applications that isexecuted on device 200. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen212.

In one embodiment, device 200 includes touch screen 212, menu button304, push button 306 for powering the device on/off and locking thedevice, volume adjustment button(s) 308, subscriber identity module(SIM) card slot 310, headset jack 312, and docking/charging externalport 224. Push button 306 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 200 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 213. Device 200 also, optionally, includes one or morecontact intensity sensors 265 for detecting intensity of contacts ontouch screen 212 and/or one or more tactile output generators 267 forgenerating tactile outputs for a user of device 200.

FIG. 4 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 400 need not be portable. In some embodiments,device 400 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 400 typically includesone or more processing units (CPUs) 410, one or more network or othercommunications interfaces 460, memory 470, and one or more communicationbuses 420 for interconnecting these components. Communication buses 420optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 400 includes input/output (I/O) interface 430 comprising display440, which is typically a touch screen display. I/O interface 430 alsooptionally includes a keyboard and/or mouse (or other pointing device)450 and touchpad 455, tactile output generator 457 for generatingtactile outputs on device 400 (e.g., similar to tactile outputgenerator(s) 267 described above with reference to FIG. 2A), sensors 459(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 265 describedabove with reference to FIG. 2A). Memory 470 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 470 optionally includes one or more storage devicesremotely located from CPU(s) 410. In some embodiments, memory 470 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 202 of portablemultifunction device 200 (FIG. 2A), or a subset thereof. Furthermore,memory 470 optionally stores additional programs, modules, and datastructures not present in memory 202 of portable multifunction device200. For example, memory 470 of device 400 optionally stores drawingmodule 480, presentation module 482, word processing module 484, websitecreation module 486, disk authoring module 488, and/or spreadsheetmodule 490, while memory 202 of portable multifunction device 200 (FIG.2A) optionally does not store these modules.

Each of the above-identified elements in FIG. 4 is, in some examples,stored in one or more of the previously mentioned memory devices. Eachof the above-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are combined or otherwise rearranged in variousembodiments. In some embodiments, memory 470 stores a subset of themodules and data structures identified above. Furthermore, memory 470stores additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces thatcan be implemented on, for example, portable multifunction device 200.

FIG. 5A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 200 in accordance withsome embodiments. Similar user interfaces are implemented on device 400.In some embodiments, user interface 500 includes the following elements,or a subset or superset thereof:

Signal strength indicator(s) 502 for wireless communication(s), such ascellular and Wi-Fi signals;

-   -   Time 504;    -   Bluetooth indicator 505;    -   Battery status indicator 506;    -   Tray 508 with icons for frequently used applications, such as:        -   Icon 516 for telephone module 238, labeled “Phone,” which            optionally includes an indicator 514 of the number of missed            calls or voicemail messages;        -   Icon 518 for e-mail client module 240, labeled “Mail,” which            optionally includes an indicator 510 of the number of unread            e-mails;        -   Icon 520 for browser module 247, labeled “Browser;” and        -   Icon 522 for video and music player module 252, also            referred to as iPod (trademark of Apple Inc.) module 252,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 524 for IM module 241, labeled “Messages;”        -   Icon 526 for calendar module 248, labeled “Calendar;”        -   Icon 528 for image management module 244, labeled “Photos;”        -   Icon 530 for camera module 243, labeled “Camera;”        -   Icon 532 for online video module 255, labeled “Online            Video;”        -   Icon 534 for stocks widget 249-2, labeled “Stocks;”        -   Icon 536 for map module 254, labeled “Maps;”        -   Icon 538 for weather widget 249-1, labeled “Weather;”        -   Icon 540 for alarm clock widget 249-4, labeled “Clock;”        -   Icon 542 for workout support module 242, labeled “Workout            Support;”        -   Icon 544 for notes module 253, labeled “Notes;” and        -   Icon 546 for a settings application or module, labeled            “Settings,” which provides access to settings for device 200            and its various applications 236.

It should be noted that the icon labels illustrated in FIG. 5A aremerely exemplary. For example, icon 522 for video and music playermodule 252 is optionally labeled “Music” or “Music Player.” Other labelsare, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 5B illustrates an exemplary user interface on a device (e.g.,device 400, FIG. 4) with a touch-sensitive surface 551 (e.g., a tabletor touchpad 455, FIG. 4) that is separate from the display 550 (e.g.,touch screen display 212). Device 400 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 457) fordetecting intensity of contacts on touch-sensitive surface 551 and/orone or more tactile output generators 459 for generating tactile outputsfor a user of device 400.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 212 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 5B. In some embodiments, the touch-sensitive surface(e.g., 551 in FIG. 5B) has a primary axis (e.g., 552 in FIG. 5B) thatcorresponds to a primary axis (e.g., 553 in FIG. 5B) on the display(e.g., 550). In accordance with these embodiments, the device detectscontacts (e.g., 560 and 562 in FIG. 5B) with the touch-sensitive surface551 at locations that correspond to respective locations on the display(e.g., in FIG. 5B, 560 corresponds to 568 and 562 corresponds to 570).In this way, user inputs (e.g., contacts 560 and 562, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,551 in FIG. 5B) are used by the device to manipulate the user interfaceon the display (e.g., 550 in FIG. 5B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 6A illustrates exemplary personal electronic device 600. Device 600includes body 602. In some embodiments, device 600 includes some or allof the features described with respect to devices 200 and 400 (e.g.,FIGS. 2A-4). In some embodiments, device 600 has touch-sensitive displayscreen 604, hereafter touch screen 604. Alternatively, or in addition totouch screen 604, device 600 has a display and a touch-sensitivesurface. As with devices 200 and 400, in some embodiments, touch screen604 (or the touch-sensitive surface) has one or more intensity sensorsfor detecting intensity of contacts (e.g., touches) being applied. Theone or more intensity sensors of touch screen 604 (or thetouch-sensitive surface) provide output data that represents theintensity of touches. The user interface of device 600 responds totouches based on their intensity, meaning that touches of differentintensities can invoke different user interface operations on device600.

Techniques for detecting and processing touch intensity are found, forexample, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 600 has one or more input mechanisms 606 and608. Input mechanisms 606 and 608, if included, are physical. Examplesof physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 600 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 600 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 600 to be worn by a user.

FIG. 6B depicts exemplary personal electronic device 600. In someembodiments, device 600 includes some or all of the components describedwith respect to FIGS. 2A, 2B, and 4. Device 600 has bus 612 thatoperatively couples I/O section 614 with one or more computer processors616 and memory 618. I/O section 614 is connected to display 604, whichcan have touch-sensitive component 622 and, optionally, touch-intensitysensitive component 624. In addition, I/O section 614 is connected withcommunication unit 630 for receiving application and operating systemdata, using Wi-Fi, Bluetooth, near field communication (NFC), cellular,and/or other wireless communication techniques. Device 600 includesinput mechanisms 606 and/or 608. Input mechanism 606 is a rotatableinput device or a depressible and rotatable input device, for example.Input mechanism 608 is a button, in some examples.

Input mechanism 608 is a microphone, in some examples. Personalelectronic device 600 includes, for example, various sensors, such asGPS sensor 632, accelerometer 634, directional sensor 640 (e.g.,compass), gyroscope 636, motion sensor 638, and/or a combinationthereof, all of which are operatively connected to I/O section 614.

Memory 618 of personal electronic device 600 is a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors616, for example, cause the computer processors to perform thetechniques and processes described below. The computer-executableinstructions, for example, are also stored and/or transported within anynon-transitory computer-readable storage medium for use by or inconnection with an instruction execution system, apparatus, or device,such as a computer-based system, processor-containing system, or othersystem that can fetch the instructions from the instruction executionsystem, apparatus, or device and execute the instructions. Personalelectronic device 600 is not limited to the components and configurationof FIG. 6B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, for example, displayed on thedisplay screen of devices 200, 400, and/or 600 (FIGS. 2A, 4, and 6A-6B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each constitutes an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 455 in FIG. 4 or touch-sensitive surface 551 in FIG. 5B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 212 in FIG. 2A or touch screen 212in FIG. 5A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds includesa first intensity threshold and a second intensity threshold. In thisexample, a contact with a characteristic intensity that does not exceedthe first threshold results in a first operation, a contact with acharacteristic intensity that exceeds the first intensity threshold anddoes not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is based ononly a portion of the continuous swipe contact, and not the entire swipecontact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm is applied to theintensities of the swipe contact prior to determining the characteristicintensity of the contact. For example, the smoothing algorithmoptionally includes one or more of: an unweighted sliding-averagesmoothing algorithm, a triangular smoothing algorithm, a median filtersmoothing algorithm, and/or an exponential smoothing algorithm. In somecircumstances, these smoothing algorithms eliminate narrow spikes ordips in the intensities of the swipe contact for purposes of determininga characteristic intensity.

The intensity of a contact on the touch-sensitive surface ischaracterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

3. Digital Assistant System

FIG. 7A illustrates a block diagram of digital assistant system 700 inaccordance with various examples. In some examples, digital assistantsystem 700 is implemented on a standalone computer system. In someexamples, digital assistant system 700 is distributed across multiplecomputers. In some examples, some of the modules and functions of thedigital assistant are divided into a server portion and a clientportion, where the client portion resides on one or more user devices(e.g., devices 104, 122, 200, 400, or 600) and communicates with theserver portion (e.g., server system 108) through one or more networks,e.g., as shown in FIG. 1. In some examples, digital assistant system 700is an implementation of server system 108 (and/or DA server 106) shownin FIG. 1. It should be noted that digital assistant system 700 is onlyone example of a digital assistant system, and that digital assistantsystem 700 can have more or fewer components than shown, can combine twoor more components, or can have a different configuration or arrangementof the components. The various components shown in FIG. 7A areimplemented in hardware, software instructions for execution by one ormore processors, firmware, including one or more signal processingand/or application specific integrated circuits, or a combinationthereof.

Digital assistant system 700 includes memory 702, one or more processors704, input/output (I/O) interface 706, and network communicationsinterface 708. These components can communicate with one another overone or more communication buses or signal lines 710.

In some examples, memory 702 includes a non-transitory computer-readablemedium, such as high-speed random access memory and/or a non-volatilecomputer-readable storage medium (e.g., one or more magnetic diskstorage devices, flash memory devices, or other non-volatile solid-statememory devices).

In some examples, I/O interface 706 couples input/output devices 716 ofdigital assistant system 700, such as displays, keyboards, touchscreens, and microphones, to user interface module 722. I/O interface706, in conjunction with user interface module 722, receives user inputs(e.g., voice input, keyboard inputs, touch inputs, etc.) and processesthem accordingly. In some examples, e.g., when the digital assistant isimplemented on a standalone user device, digital assistant system 700includes any of the components and I/O communication interfacesdescribed with respect to devices 200, 400, or 600 in FIGS. 2A, 4,6A-6B, respectively. In some examples, digital assistant system 700represents the server portion of a digital assistant implementation, andcan interact with the user through a client-side portion residing on auser device (e.g., devices 104, 200, 400, or 600).

In some examples, the network communications interface 708 includeswired communication port(s) 712 and/or wireless transmission andreception circuitry 714. The wired communication port(s) receives andsend communication signals via one or more wired interfaces, e.g.,Ethernet, Universal Serial Bus (USB), FIREWIRE, etc. The wirelesscircuitry 714 receives and sends RF signals and/or optical signalsfrom/to communications networks and other communications devices. Thewireless communications use any of a plurality of communicationsstandards, protocols, and technologies, such as GSM, EDGE, CDMA, TDMA,Bluetooth, Wi-Fi, VoIP, Wi-MAX, or any other suitable communicationprotocol. Network communications interface 708 enables communicationbetween digital assistant system 700 with networks, such as theInternet, an intranet, and/or a wireless network, such as a cellulartelephone network, a wireless local area network (LAN), and/or ametropolitan area network (MAN), and other devices.

In some examples, memory 702, or the computer-readable storage media ofmemory 702, stores programs, modules, instructions, and data structuresincluding all or a subset of: operating system 718, communicationsmodule 720, user interface module 722, one or more applications 724, anddigital assistant module 726. In particular, memory 702, or thecomputer-readable storage media of memory 702, stores instructions forperforming the processes described below. One or more processors 704execute these programs, modules, and instructions, and reads/writesfrom/to the data structures.

Operating system 718 (e.g., Darwin, RTXC, LINUX, UNIX, iOS, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communications between varioushardware, firmware, and software components.

Communications module 720 facilitates communications between digitalassistant system 700 with other devices over network communicationsinterface 708. For example, communications module 720 communicates withRF circuitry 208 of electronic devices such as devices 200, 400, and 600shown in FIGS. 2A, 4, 6A-6B, respectively. Communications module 720also includes various components for handling data received by wirelesscircuitry 714 and/or wired communications port 712.

User interface module 722 receives commands and/or inputs from a uservia I/O interface 706 (e.g., from a keyboard, touch screen, pointingdevice, controller, and/or microphone), and generate user interfaceobjects on a display. User interface module 722 also prepares anddelivers outputs (e.g., speech, sound, animation, text, icons,vibrations, haptic feedback, light, etc.) to the user via the I/Ointerface 706 (e.g., through displays, audio channels, speakers,touch-pads, etc.).

Applications 724 include programs and/or modules that are configured tobe executed by one or more processors 704. For example, if the digitalassistant system is implemented on a standalone user device,applications 724 include user applications, such as games, a calendarapplication, a navigation application, or an email application. Ifdigital assistant system 700 is implemented on a server, applications724 include resource management applications, diagnostic applications,or scheduling applications, for example.

Memory 702 also stores digital assistant module 726 (or the serverportion of a digital assistant). In some examples, digital assistantmodule 726 includes the following sub-modules, or a subset or supersetthereof: input/output processing module 728, speech-to-text (STT)processing module 730, natural language processing module 732, dialogueflow processing module 734, task flow processing module 736, serviceprocessing module 738, and speech synthesis processing module 740. Eachof these modules has access to one or more of the following systems ordata and models of the digital assistant module 726, or a subset orsuperset thereof: ontology 760, vocabulary index 744, user data 748,task flow models 754, service models 756, and ASR systems 758.

In some examples, using the processing modules, data, and modelsimplemented in digital assistant module 726, the digital assistant canperform at least some of the following: converting speech input intotext; identifying a user's intent expressed in a natural language inputreceived from the user; actively eliciting and obtaining informationneeded to fully infer the user's intent (e.g., by disambiguating words,games, intentions, etc.); determining the task flow for fulfilling theinferred intent; and executing the task flow to fulfill the inferredintent.

In some examples, as shown in FIG. 7B, I/O processing module 728interacts with the user through I/O devices 716 in FIG. 7A or with auser device (e.g., devices 104, 200, 400, or 600) through networkcommunications interface 708 in FIG. 7A to obtain user input (e.g., aspeech input) and to provide responses (e.g., as speech outputs) to theuser input. I/O processing module 728 optionally obtains contextualinformation associated with the user input from the user device, alongwith or shortly after the receipt of the user input. The contextualinformation includes user-specific data, vocabulary, and/or preferencesrelevant to the user input. In some examples, the contextual informationalso includes software and hardware states of the user device at thetime the user request is received, and/or information related to thesurrounding environment of the user at the time that the user requestwas received. In some examples, I/O processing module 728 also sendsfollow-up questions to, and receive answers from, the user regarding theuser request. When a user request is received by I/O processing module728 and the user request includes speech input, I/O processing module728 forwards the speech input to STT processing module 730 (or speechrecognizer) for speech-to-text conversions.

STT processing module 730 includes one or more ASR systems 758. The oneor more ASR systems 758 can process the speech input that is receivedthrough I/O processing module 728 to produce a recognition result. EachASR system 758 includes a front-end speech pre-processor. The front-endspeech pre-processor extracts representative features from the speechinput. For example, the front-end speech pre-processor performs aFourier transform on the speech input to extract spectral features thatcharacterize the speech input as a sequence of representativemulti-dimensional vectors. Further, each ASR system 758 includes one ormore speech recognition models (e.g., acoustic models and/or languagemodels) and implements one or more speech recognition engines. Examplesof speech recognition models include Hidden Markov Models,Gaussian-Mixture Models, Deep Neural Network Models, n-gram languagemodels, and other statistical models. Examples of speech recognitionengines include the dynamic time warping based engines and weightedfinite-state transducers (WFST) based engines. The one or more speechrecognition models and the one or more speech recognition engines areused to process the extracted representative features of the front-endspeech pre-processor to produce intermediate recognitions results (e.g.,phonemes, phonemic strings, and sub-words), and ultimately, textrecognition results (e.g., words, word strings, or sequence of tokens).In some examples, the speech input is processed at least partially by athird-party service or on the user's device (e.g., device 104, 200, 400,or 600) to produce the recognition result. Once STT processing module730 produces recognition results containing a text string (e.g., words,or sequence of words, or sequence of tokens), the recognition result ispassed to natural language processing module 732 for intent deduction.In some examples, STT processing module 730 produces multiple candidatetext representations of the speech input. Each candidate textrepresentation is a sequence of words or tokens corresponding to thespeech input. In some examples, each candidate text representation isassociated with a speech recognition confidence score. Based on thespeech recognition confidence scores, STT processing module 730 ranksthe candidate text representations and provides the n-best (e.g., nhighest ranked) candidate text representation(s) to natural languageprocessing module 732 for intent deduction, where n is a predeterminedinteger greater than zero. For example, in one example, only the highestranked (n=1) candidate text representation is passed to natural languageprocessing module 732 for intent deduction. In another example, the fivehighest ranked (n=5) candidate text representations are passed tonatural language processing module 732 for intent deduction.

More details on the speech-to-text processing are described in U.S.Utility application Ser. No. 13/236,942 for “Consolidating SpeechRecognition Results,” filed on Sep. 20, 2011, the entire disclosure ofwhich is incorporated herein by reference.

In some examples, STT processing module 730 includes and/or accesses avocabulary of recognizable words via phonetic alphabet conversion module731. Each vocabulary word is associated with one or more candidatepronunciations of the word represented in a speech recognition phoneticalphabet. In particular, the vocabulary of recognizable words includes aword that is associated with a plurality of candidate pronunciations.For example, the vocabulary includes the word “tomato” that isassociated with the candidate pronunciations of /

/ and /

/. Further, vocabulary words are associated with custom candidatepronunciations that are based on previous speech inputs from the user.Such custom candidate pronunciations are stored in STT processing module730 and are associated with a particular user via the user's profile onthe device. In some examples, the candidate pronunciations for words aredetermined based on the spelling of the word and one or more linguisticand/or phonetic rules. In some examples, the candidate pronunciationsare manually generated, e.g., based on known canonical pronunciations.

In some examples, the candidate pronunciations are ranked based on thecommonness of the candidate pronunciation. For example, the candidatepronunciation /

/ is ranked higher than /

/, because the former is a more commonly used pronunciation (e.g., amongall users, for users in a particular geographical region, or for anyother appropriate subset of users). In some examples, candidatepronunciations are ranked based on whether the candidate pronunciationis a custom candidate pronunciation associated with the user. Forexample, custom candidate pronunciations are ranked higher thancanonical candidate pronunciations. This can be useful for recognizingproper nouns having a unique pronunciation that deviates from canonicalpronunciation. In some examples, candidate pronunciations are associatedwith one or more speech characteristics, such as geographic origin,nationality, or ethnicity. For example, the candidate pronunciation /

/ is associated with the United States, whereas the candidatepronunciation /

/ is associated with Great Britain. Further, the rank of the candidatepronunciation is based on one or more characteristics (e.g., geographicorigin, nationality, ethnicity, etc.) of the user stored in the user'sprofile on the device. For example, it can be determined from the user'sprofile that the user is associated with the United States. Based on theuser being associated with the United States, the candidatepronunciation /

/ (associated with the United States) is ranked higher than thecandidate pronunciation /

/ (associated with Great Britain). In some examples, one of the rankedcandidate pronunciations is selected as a predicted pronunciation (e.g.,the most likely pronunciation).

When a speech input is received, STT processing module 730 is used todetermine the phonemes corresponding to the speech input (e.g., using anacoustic model), and then attempt to determine words that match thephonemes (e.g., using a language model). For example, if STT processingmodule 730 first identifies the sequence of phonemes /

/ corresponding to a portion of the speech input, it can then determine,based on vocabulary index 744, that this sequence corresponds to theword “tomato.”

In some examples, STT processing module 730 uses approximate matchingtechniques to determine words in an utterance. Thus, for example, theSTT processing module 730 determines that the sequence of phonemes /

/ corresponds to the word “tomato,” even if that particular sequence ofphonemes is not one of the candidate sequence of phonemes for that word.

Natural language processing module 732 (“natural language processor”) ofthe digital assistant takes the n-best candidate text representation(s)(“word sequence(s)” or “token sequence(s)”) generated by STT processingmodule 730, and attempts to associate each of the candidate textrepresentations with one or more “actionable intents” recognized by thedigital assistant. An “actionable intent” (or “user intent”) representsa task that can be performed by the digital assistant, and can have anassociated task flow implemented in task flow models 754. The associatedtask flow is a series of programmed actions and steps that the digitalassistant takes in order to perform the task. The scope of a digitalassistant's capabilities is dependent on the number and variety of taskflows that have been implemented and stored in task flow models 754, orin other words, on the number and variety of “actionable intents” thatthe digital assistant recognizes. The effectiveness of the digitalassistant, however, also dependents on the assistant's ability to inferthe correct “actionable intent(s)” from the user request expressed innatural language.

In some examples, in addition to the sequence of words or tokensobtained from STT processing module 730, natural language processingmodule 732 also receives contextual information associated with the userrequest, e.g., from I/O processing module 728. The natural languageprocessing module 732 optionally uses the contextual information toclarify, supplement, and/or further define the information contained inthe candidate text representations received from STT processing module730. The contextual information includes, for example, user preferences,hardware, and/or software states of the user device, sensor informationcollected before, during, or shortly after the user request, priorinteractions (e.g., dialogue) between the digital assistant and theuser, and the like. As described herein, contextual information is, insome examples, dynamic, and changes with time, location, content of thedialogue, and other factors.

In some examples, the natural language processing is based on, e.g.,ontology 760. Ontology 760 is a hierarchical structure containing manynodes, each node representing either an “actionable intent” or a“property” relevant to one or more of the “actionable intents” or other“properties.” As noted above, an “actionable intent” represents a taskthat the digital assistant is capable of performing, i.e., it is“actionable” or can be acted on. A “property” represents a parameterassociated with an actionable intent or a sub-aspect of anotherproperty. A linkage between an actionable intent node and a propertynode in ontology 760 defines how a parameter represented by the propertynode pertains to the task represented by the actionable intent node.

In some examples, ontology 760 is made up of actionable intent nodes andproperty nodes. Within ontology 760, each actionable intent node islinked to one or more property nodes either directly or through one ormore intermediate property nodes. Similarly, each property node islinked to one or more actionable intent nodes either directly or throughone or more intermediate property nodes. For example, as shown in FIG.7C, ontology 760 includes a “restaurant reservation” node (i.e., anactionable intent node). Property nodes “restaurant,” “date/time” (forthe reservation), and “party size” are each directly linked to theactionable intent node (i.e., the “restaurant reservation” node).

In addition, property nodes “cuisine,” “price range,” “phone number,”and “location” are sub-nodes of the property node “restaurant,” and areeach linked to the “restaurant reservation” node (i.e., the actionableintent node) through the intermediate property node “restaurant.” Foranother example, as shown in FIG. 7C, ontology 760 also includes a “setreminder” node (i.e., another actionable intent node). Property nodes“date/time” (for setting the reminder) and “subject” (for the reminder)are each linked to the “set reminder” node. Since the property“date/time” is relevant to both the task of making a restaurantreservation and the task of setting a reminder, the property node“date/time” is linked to both the “restaurant reservation” node and the“set reminder” node in ontology 760.

An actionable intent node, along with its linked property nodes, isdescribed as a “domain.” In the present discussion, each domain isassociated with a respective actionable intent, and refers to the groupof nodes (and the relationships there between) associated with theparticular actionable intent. For example, ontology 760 shown in FIG. 7Cincludes an example of restaurant reservation domain 762 and an exampleof reminder domain 764 within ontology 760. The restaurant reservationdomain includes the actionable intent node “restaurant reservation,”property nodes “restaurant,” “date/time,” and “party size,” andsub-property nodes “cuisine,” “price range,” “phone number,” and“location.” Reminder domain 764 includes the actionable intent node “setreminder,” and property nodes “subject” and “date/time.” In someexamples, ontology 760 is made up of many domains. Each domain sharesone or more property nodes with one or more other domains. For example,the “date/time” property node is associated with many different domains(e.g., a scheduling domain, a travel reservation domain, a movie ticketdomain, etc.), in addition to restaurant reservation domain 762 andreminder domain 764.

While FIG. 7C illustrates two example domains within ontology 760, otherdomains include, for example, “find a movie,” “initiate a phone call,”“find directions,” “schedule a meeting,” “send a message,” and “providean answer to a question,” “read a list,” “providing navigationinstructions,” “provide instructions for a task” and so on. A “send amessage” domain is associated with a “send a message” actionable intentnode, and further includes property nodes such as “recipient(s),”“message type,” and “message body.” The property node “recipient” isfurther defined, for example, by the sub-property nodes such as“recipient name” and “message address.”

In some examples, ontology 760 includes all the domains (and henceactionable intents) that the digital assistant is capable ofunderstanding and acting upon. In some examples, ontology 760 ismodified, such as by adding or removing entire domains or nodes, or bymodifying relationships between the nodes within the ontology 760.

In some examples, nodes associated with multiple related actionableintents are clustered under a “super domain” in ontology 760. Forexample, a “travel” super-domain includes a cluster of property nodesand actionable intent nodes related to travel. The actionable intentnodes related to travel includes “airline reservation,” “hotelreservation,” “car rental,” “get directions,” “find points of interest,”and so on. The actionable intent nodes under the same super domain(e.g., the “travel” super domain) have many property nodes in common.For example, the actionable intent nodes for “airline reservation,”“hotel reservation,” “car rental,” “get directions,” and “find points ofinterest” share one or more of the property nodes “start location,”“destination,” “departure date/time,” “arrival date/time,” and “partysize.”

In some examples, each node in ontology 760 is associated with a set ofwords and/or phrases that are relevant to the property or actionableintent represented by the node. The respective set of words and/orphrases associated with each node are the so-called “vocabulary”associated with the node. The respective set of words and/or phrasesassociated with each node are stored in vocabulary index 744 inassociation with the property or actionable intent represented by thenode. For example, returning to FIG. 7B, the vocabulary associated withthe node for the property of “restaurant” includes words such as “food,”“drinks,” “cuisine,” “hungry,” “eat,” “pizza,” “fast food,” “meal,” andso on. For another example, the vocabulary associated with the node forthe actionable intent of “initiate a phone call” includes words andphrases such as “call,” “phone,” “dial,” “ring,” “call this number,”“make a call to,” and so on. The vocabulary index 744 optionallyincludes words and phrases in different languages.

Natural language processing module 732 receives the candidate textrepresentations (e.g., text string(s) or token sequence(s)) from STTprocessing module 730, and for each candidate representation, determineswhat nodes are implicated by the words in the candidate textrepresentation. In some examples, if a word or phrase in the candidatetext representation is found to be associated with one or more nodes inontology 760 (via vocabulary index 744), the word or phrase “triggers”or “activates” those nodes. Based on the quantity and/or relativeimportance of the activated nodes, natural language processing module732 selects one of the actionable intents as the task that the userintended the digital assistant to perform. In some examples, the domainthat has the most “triggered” nodes is selected. In some examples, thedomain having the highest confidence value (e.g., based on the relativeimportance of its various triggered nodes) is selected. In someexamples, the domain is selected based on a combination of the numberand the importance of the triggered nodes. In some examples, additionalfactors are considered in selecting the node as well, such as whetherthe digital assistant has previously correctly interpreted a similarrequest from a user.

User data 748 includes user-specific information, such as user-specificvocabulary, user preferences, user address, user's default and secondarylanguages, user's contact list, and other short-term or long-terminformation for each user. In some examples, natural language processingmodule 732 uses the user-specific information to supplement theinformation contained in the user input to further define the userintent. For example, for a user request “invite my friends to mybirthday party,” natural language processing module 732 is able toaccess user data 748 to determine who the “friends” are and when andwhere the “birthday party” would be held, rather than requiring the userto provide such information explicitly in his/her request.

It should be recognized that in some examples, natural languageprocessing module 732 is implemented using one or more machine learningmechanisms (e.g., neural networks). In particular, the one or moremachine learning mechanisms are configured to receive a candidate textrepresentation and contextual information associated with the candidatetext representation. Based on the candidate text representation and theassociated contextual information, the one or more machine learningmechanisms are configured to determine intent confidence scores over aset of candidate actionable intents. Natural language processing module732 can select one or more candidate actionable intents from the set ofcandidate actionable intents based on the determined intent confidencescores. In some examples, an ontology (e.g., ontology 760) is also usedto select the one or more candidate actionable intents from the set ofcandidate actionable intents.

Other details of searching an ontology based on a token string aredescribed in U.S. Utility application Ser. No. 12/341,743 for “Methodand Apparatus for Searching Using An Active Ontology,” filed Dec. 22,2008, the entire disclosure of which is incorporated herein byreference.

In some examples, once natural language processing module 732 identifiesan actionable intent (or domain) based on the user request, naturallanguage processing module 732 generates a structured query to representthe identified actionable intent. In some examples, the structured queryincludes parameters for one or more nodes within the domain for theactionable intent, and at least some of the parameters are populatedwith the specific information and requirements specified in the userrequest. For example, the user says “Make me a dinner reservation at asushi place at 7.” In this case, natural language processing module 732is able to correctly identify the actionable intent to be “restaurantreservation” based on the user input. According to the ontology, astructured query for a “restaurant reservation” domain includesparameters such as {Cuisine}, {Time}, {Date}, {Party Size}, and thelike. In some examples, based on the speech input and the text derivedfrom the speech input using STT processing module 730, natural languageprocessing module 732 generates a partial structured query for therestaurant reservation domain, where the partial structured queryincludes the parameters {Cuisine=“Sushi”} and {Time=“7 pm”}. However, inthis example, the user's utterance contains insufficient information tocomplete the structured query associated with the domain. Therefore,other necessary parameters such as {Party Size} and {Date} are notspecified in the structured query based on the information currentlyavailable. In some examples, natural language processing module 732populates some parameters of the structured query with receivedcontextual information. For example, in some examples, if the userrequested a sushi restaurant “near me,” natural language processingmodule 732 populates a {location} parameter in the structured query withGPS coordinates from the user device.

In some examples, natural language processing module 732 identifiesmultiple candidate actionable intents for each candidate textrepresentation received from STT processing module 730. Further, in someexamples, a respective structured query (partial or complete) isgenerated for each identified candidate actionable intent. Naturallanguage processing module 732 determines an intent confidence score foreach candidate actionable intent and ranks the candidate actionableintents based on the intent confidence scores. In some examples, naturallanguage processing module 732 passes the generated structured query (orqueries), including any completed parameters, to task flow processingmodule 736 (“task flow processor”). In some examples, the structuredquery (or queries) for the m-best (e.g., m highest ranked) candidateactionable intents are provided to task flow processing module 736,where m is a predetermined integer greater than zero. In some examples,the structured query (or queries) for the m-best candidate actionableintents are provided to task flow processing module 736 with thecorresponding candidate text representation(s).

Other details of inferring a user intent based on multiple candidateactionable intents determined from multiple candidate textrepresentations of a speech input are described in U.S. Utilityapplication Ser. No. 14/298,725 for “System and Method for InferringUser Intent From Speech Inputs,” filed Jun. 6, 2014, the entiredisclosure of which is incorporated herein by reference.

Task flow processing module 736 is configured to receive the structuredquery (or queries) from natural language processing module 732, completethe structured query, if necessary, and perform the actions required to“complete” the user's ultimate request. In some examples, the variousprocedures necessary to complete these tasks are provided in task flowmodels 754. In some examples, task flow models 754 include proceduresfor obtaining additional information from the user and task flows forperforming actions associated with the actionable intent.

As described above, in order to complete a structured query, task flowprocessing module 736 needs to initiate additional dialogue with theuser in order to obtain additional information, and/or disambiguatepotentially ambiguous utterances. When such interactions are necessary,task flow processing module 736 invokes dialogue flow processing module734 to engage in a dialogue with the user. In some examples, dialogueflow processing module 734 determines how (and/or when) to ask the userfor the additional information and receives and processes the userresponses. The questions are provided to and answers are received fromthe users through I/O processing module 728. In some examples, dialogueflow processing module 734 presents dialogue output to the user viaaudio and/or visual output, and receives input from the user via spokenor physical (e.g., clicking) responses. Continuing with the exampleabove, when task flow processing module 736 invokes dialogue flowprocessing module 734 to determine the “party size” and “date”information for the structured query associated with the domain“restaurant reservation,” dialogue flow processing module 734 generatesquestions such as “For how many people?” and “On which day?” to pass tothe user. Once answers are received from the user, dialogue flowprocessing module 734 then populates the structured query with themissing information, or pass the information to task flow processingmodule 736 to complete the missing information from the structuredquery.

Once task flow processing module 736 has completed the structured queryfor an actionable intent, task flow processing module 736 proceeds toperform the ultimate task associated with the actionable intent.Accordingly, task flow processing module 736 executes the steps andinstructions in the task flow model according to the specific parameterscontained in the structured query. For example, the task flow model forthe actionable intent of “restaurant reservation” includes steps andinstructions for contacting a restaurant and actually requesting areservation for a particular party size at a particular time. Forexample, using a structured query such as: {restaurant reservation,restaurant=ABC Café, date=3/12/2012, time=7 pm, party size=5}, task flowprocessing module 736 performs the steps of: (1) logging onto a serverof the ABC Café or a restaurant reservation system such as OPENTABLE®,(2) entering the date, time, and party size information in a form on thewebsite, (3) submitting the form, and (4) making a calendar entry forthe reservation in the user's calendar.

In some examples, task flow processing module 736 employs the assistanceof service processing module 738 (“service processing module”) tocomplete a task requested in the user input or to provide aninformational answer requested in the user input. For example, serviceprocessing module 738 acts on behalf of task flow processing module 736to make a phone call, set a calendar entry, invoke a map search, invokeor interact with other user applications installed on the user device,and invoke or interact with third-party services (e.g., a restaurantreservation portal, a social networking website, a banking portal,etc.). In some examples, the protocols and application programminginterfaces (API) required by each service are specified by a respectiveservice model among service models 756. Service processing module 738accesses the appropriate service model for a service and generatesrequests for the service in accordance with the protocols and APIsrequired by the service according to the service model.

For example, if a restaurant has enabled an online reservation service,the restaurant submits a service model specifying the necessaryparameters for making a reservation and the APIs for communicating thevalues of the necessary parameter to the online reservation service.When requested by task flow processing module 736, service processingmodule 738 establishes a network connection with the online reservationservice using the web address stored in the service model, and sends thenecessary parameters of the reservation (e.g., time, date, party size)to the online reservation interface in a format according to the API ofthe online reservation service.

In some examples, natural language processing module 732, dialogue flowprocessing module 734, and task flow processing module 736 are usedcollectively and iteratively to infer and define the user's intent,obtain information to further clarify and refine the user intent, andfinally generate a response (i.e., an output to the user, or thecompletion of a task) to fulfill the user's intent. The generatedresponse is a dialogue response to the speech input that at leastpartially fulfills the user's intent. Further, in some examples, thegenerated response is output as a speech output. In these examples, thegenerated response is sent to speech synthesis processing module 740(e.g., speech synthesizer) where it can be processed to synthesize thedialogue response in speech form. In yet other examples, the generatedresponse is data content relevant to satisfying a user request in thespeech input.

In examples where task flow processing module 736 receives multiplestructured queries from natural language processing module 732, taskflow processing module 736 initially processes the first structuredquery of the received structured queries to attempt to complete thefirst structured query and/or execute one or more tasks or actionsrepresented by the first structured query. In some examples, the firststructured query corresponds to the highest ranked actionable intent. Inother examples, the first structured query is selected from the receivedstructured queries based on a combination of the corresponding speechrecognition confidence scores and the corresponding intent confidencescores. In some examples, if task flow processing module 736 encountersan error during processing of the first structured query (e.g., due toan inability to determine a necessary parameter), the task flowprocessing module 736 can proceed to select and process a secondstructured query of the received structured queries that corresponds toa lower ranked actionable intent. The second structured query isselected, for example, based on the speech recognition confidence scoreof the corresponding candidate text representation, the intentconfidence score of the corresponding candidate actionable intent, amissing necessary parameter in the first structured query, or anycombination thereof.

Speech synthesis processing module 740 is configured to synthesizespeech outputs for presentation to the user. Speech synthesis processingmodule 740 synthesizes speech outputs based on text provided by thedigital assistant. For example, the generated dialogue response is inthe form of a text string. Speech synthesis processing module 740converts the text string to an audible speech output. Speech synthesisprocessing module 740 uses any appropriate speech synthesis technique inorder to generate speech outputs from text, including, but not limited,to concatenative synthesis, unit selection synthesis, diphone synthesis,domain-specific synthesis, formant synthesis, articulatory synthesis,hidden Markov model (HMM) based synthesis, and sinewave synthesis. Insome examples, speech synthesis processing module 740 is configured tosynthesize individual words based on phonemic strings corresponding tothe words. For example, a phonemic string is associated with a word inthe generated dialogue response. The phonemic string is stored inmetadata associated with the word. Speech synthesis processing module740 is configured to directly process the phonemic string in themetadata to synthesize the word in speech form.

In some examples, instead of (or in addition to) using speech synthesisprocessing module 740, speech synthesis is performed on a remote device(e.g., the server system 108), and the synthesized speech is sent to theuser device for output to the user. For example, this can occur in someimplementations where outputs for a digital assistant are generated at aserver system. And because server systems generally have more processingpower or resources than a user device, it is possible to obtain higherquality speech outputs than would be practical with client-sidesynthesis.

Additional details on digital assistants can be found in the U.S.Utility application Ser. No. 12/987,982, entitled “Intelligent AutomatedAssistant,” filed Jan. 10, 2011, and U.S. Utility application Ser. No.13/251,088, entitled “Generating and Processing Task Items ThatRepresent Tasks to Perform,” filed Sep. 30, 2011, the entire disclosuresof which are incorporated herein by reference.

4. System and Technique for Electing a Context Collector of aContext-Sharing Group

FIG. 8 illustrates a system and technique for electing a contextcollector of a device circle, according to various examples. System 800includes user device 802, communal device 804, user device 806, and userdevice 808. User device 802, user device 806, and user device 808 areall client devices (e.g., user devices 104, 122, 200, 400, or 600). Forexample, user device 802 is an iPhone®, user device 806 is an AppleWatch®, and user device 808 is an iPad®. A client device is registeredto a single user. For example, user device 802 may be registered to afirst user and user device 806 and user device 808 may be registered toa second user. Communal device 804 is a smart speaker that has the sameor similar digital assistant capabilities as the various user devices. Acommunal device is an electronic device that is not registered to asingle user or that is registered to multiple users (e.g., such that thecommunal device may be used by multiple users without additional userregistration and/or user authentication requirements). For example,communal device 804 is a HomePod®. Another example of a communal deviceis a smart TV (e.g., Apple TV®).

System 800 further includes network 810. Network 810 is a wirelesscommunications network (e.g., network(s) 110). In some examples, system800 includes one or more remote devices (e.g., one or more remoteservers (e.g., DA server 106), a local server, a cloud-computing system,or the like). It should be recognized that, in these examples, any ofthe operations performed by user device 802, communal device 804, userdevice 806, and/or user device 808 can instead be performed by the oneor more remote devices. For example, the one or more servers can performthe operations of the respective DA client modules (e.g., DA clientmodule 229) of user device 802, communal device 804, user device 806,and/or user device 808.

As represented by arrow 812, user device 802 connects to network 810. Atthis point in the process, communal device 804, user device 806, anduser device 808 are also connected to network 810. After user device 802connects to network 810, user 802 joins context-sharing group 814, whichalso includes communal device 804, user device 806, and user device 808.A “context-sharing group” (also referred to as a “device circle”) is acollection of two or more electronic devices (e.g., within a specificlocation) that share context information with at least one electronicdevice participating in the context-sharing group (e.g., with a “contextcollector” of the context-sharing group). Context-sharing group 814 isassociated with a specific location (e.g., a home, an office, or thelike). As such, the electronic devices participating in context-sharinggroup 814 are each located in an area (e.g., a room, a floor, or thelike) of the specific location. In some examples, context-sharing group814 is not associated with a specific location and thus the electronicdevices participating in context-sharing group 814 do not need to belocated in a single location (e.g., the electronic devices may belocated in two separate homes).

In some examples, electronic devices participating in a context-sharinggroup automatically share context information with a “context collector”of the context-sharing group in response to undergoing a “device statechange” (device state changes are described in greater detail below). Acontext collector is an electronic device that receives, aggregates, andstores context information from electronic devices participating in thecontext-sharing group. Further, a context collector provides the“aggregate context” of the context-sharing group (which includes contextinformation received from one or more electronic devices participatingin the context-sharing group) to one or more electronic devicesparticipating in the context-sharing group (e.g., in response to, forexample, requests for the aggregated context information received fromthe one or more electronic devices). In some examples, the contextcollector of a context-sharing group is an electronic device (e.g., auser device or a communal device) that is participating in thecontext-sharing group. In other examples, the context collector is aremote device that is not participating in the context-sharing group andthus does not share its own context information with the electronicdevices participating in the context-sharing group. Examples of remotedevices that can serve as a context collector include one or moreservers (e.g., DA server 106), one or more cloud-computing systems, oneor more local servers, or the like.

As will be described below with reference to FIG. 8, an electronicdevice participating in the context-sharing group is first “elected”(i.e., selected) to be the context collector before it begins receivingand aggregating context information from the other electronic devicesparticipating in the context-sharing group. Note, while FIG. 8 and thecorresponding description below discuss the election of a single contextcollector for context-sharing group 814, in some examples,context-sharing group 814 includes more than one context collector(e.g., two or three context collectors).

In some examples, user device 802 automatically joins context-sharinggroup 814 in response to connecting to network 810. In some examples,user device 802 must connect to network 810 in order to joincontext-sharing group 814. In these examples, each of the electronicdevices participating in context-sharing group 814 are also connected tonetwork 810. In other words, in these examples, each electronic deviceparticipating in context-sharing group 814 must be connected to network810. In some examples, user device 802 joins context-sharing group 814without having to connect to network 810. In some of these examples,user device 802 joins context-sharing group 814 upon establishing acommunications connection (e.g., a short distance communicationsconnection (e.g., a Bluetooth connection, a Bluetooth Low Energy (BTLE)connection, or the like)) with at least one electronic device that isalready participating in the context-sharing group (e.g., with communaldevice 804).

In some examples, user device 802 must be enrolled in context-sharinggroup 814 in order to join context-sharing group 814. For example,enrolling user device 802 in context-sharing group 814 may include auser of user device 802 registering user device 802 with context-sharinggroup 814 via a software application stored on user device 802 that hascontext-sharing group functionality (e.g., via the HomeKit® application)and/or via a web site that has context-sharing group functionality. Thismay include user device 802 registering with an already-existingcontext-sharing group 814 (e.g., created by another electronic deviceparticipating in context-sharing group 814) or creating context-sharinggroup 814 and subsequently registering with context-sharing group 814after it has been created. In some examples, enrolling incontext-sharing group 814 includes user device 802 granting accessto/allowing other electronic devices enrolled in context-sharing group814 to receive, share, store, and/or utilize context information,personal information (e.g., email addresses, home addresses, paymentinformation, or the like), and/or user data (e.g., a user's media,contacts, speech profiles, preferences, or the like) associated withuser device 802 (which includes context information, user data, and/orpersonal information locally stored on user device 802 and/or remotelystored on one or more remote devices (e.g., synced from user device 802onto one or more servers)).

In the above examples, prior to user device 802 joining context-sharinggroup 814, user device 802 determines whether or not it is enrolled incontext-sharing group 814. Then, user device 802 joins context-sharinggroup 813 only if it determines that it is enrolled in context-sharinggroup 814. If user device 802 determines that is it not enrolled incontext-sharing group 814, user device 802 forgoes joiningcontext-sharing group 814.

After user device 802 joins context-sharing group 814 (e.g., immediatelyafter or soon after (e.g., several minutes after)), the electronicdevices participating in context-sharing group 814 perform a contextcollector “election,” which is a process via which one electronic deviceof the electronic devices participating in context-sharing group 814 iselected (i.e., selected) as a context collector of the context-sharinggroup. As mentioned above, in some examples, more than one electronicdevice participating in context-sharing group 814 is elected as contextcollector. In some examples, user device 802 (and the other electronicdevices participating in context-sharing group 814) performs the contextcollector election in response to joining context-sharing group 814(e.g., immediately after joining). In some examples, user device 802(and the other electronic devices participating in context-sharing group814) performs the context collector election in response to anelectronic device participating in context-sharing group 814 (e.g., acurrent context collector) leaving the context-sharing group (e.g.,disconnecting from network 810, disconnecting from a communicationsconnection with another electronic device participating incontext-sharing group 814, and/or leaving the specific locationassociated with context-sharing group 814). Note, as will be discussedbelow, the electronic devices participating in context-sharing group 814may perform a context collector election even if context-sharing group814 already includes a context collector and even if context-sharinggroup 814 only allows for a single context collector.

The context collector election begins with user device 802 (and each ofthe other electronic devices participating in context-sharing group 814)determining a collector score based on a strength of connectivitybetween user device 802 and network 810 and/or based on a power sourcestatus of user device 802 (e.g., wired power connection versus batterypower and/or amount of battery power remaining). For example, a strongerconnection between user device 802 and network 810 will result in ahigher context collector score. Similarly, the more stable the powersource of user device 802 is, the higher the context collector score foruser device 802 will be (e.g., with a wired power connection being morestable than battery power, and with a full battery being more stablethan a low battery). In some examples, the collector score is furtherbased on a frequency of movement of user device 802 in and out ofcontext-sharing group 814 (e.g., a frequency of user device 802connecting to/disconnecting from network 810 and/or a frequency of userdevice 802 entering and/or leaving the specific location associated withcontext-sharing group 814). In some examples, the context collectorscore is further based on a stability with which user device 802 holdscontext information in its memory. In some examples, the contextcollector score is further based on a stability of communicationconnections between user device 802 and the other electronic devicesparticipating in context-sharing group 814. In some examples, thecontext collector score is further based on a reachability of userdevice 802 to other electronic devices participating in context-sharinggroup 814 (e.g., the more devices user device 802 can reach throughvarious network/other communication protocols, the higher the contextcollector score). The above factors that are considered when determininga context collector score emphasize the stability of an electronicdevice's participation in a context-sharing group, ability tocommunicate with other electronic devices, and/or ability to storecontext information, as it is desirable for context-sharing group 814 tohave a context collector that is available as often as possible toreceive, aggregate, store, and/or transmit context information.

As represented by arrows 816, after user device 802 determines a contextcollector score, user device 802 transmits the context collector score(e.g., data corresponding to the context collector score) to each of theother electronic devices participating in context-sharing group 814(i.e., communal device 804, user device 806, and user device 808) vianetwork 810. In some examples, user device 802 further transmits acontext collector indication (also referred to as a context collector“flag”) that indicates whether or not user device 802 is currently acontext collector. For example, user device 802 transmits the contextcollector indication at the same time as, or soon after, transmittingits context collector score. The context collector indication of userdevice 802 will indicate that user device 802 is a context collector if(1) user device 802 was previously elected as context collector afterjoining context-sharing group 814 (i.e., after connecting to network 810as represented by arrow 812) and/or if (2) user device 802 was electedas context collector the last time user device 802 participated incontext-sharing group 814 (i.e., prior to leaving context-sharing group814 and once again joining context-sharing 814 after connecting tonetwork 810 as represented by arrow 812). Otherwise, the contextcollector indication will indicate that user device 802 is not a contextcollector.

As represented by arrows 818, communal device 804, user device 806, anduser device 808 each transmit their respective context collector scores(and, in some examples, their respective context collector indications)to user device 802 before, at the same time, or soon after user device802 transmits is context collector score (and, in some examples, itscontext collector indication as represented by arrow 816). Although notshown in FIG. 8, communal device 804, user device 806, and user device808 also transmit their respective context collector scores (and, insome examples, their respective context collector indications) to oneanother. In this manner, after arrows 816 and arrows 818, eachelectronic device that is participating in context-sharing group 814will possess a context collector score (and, in some examples, a contextcollector indication) corresponding to each of the other electronicdevices participating in context-sharing group 814.

After receiving the context collector scores, user device 802 (and theother electronic devices participating in context-sharing group 814)determines which electronic device of the electronic devicesparticipating in context-sharing group 814 to elect as the contextcollector based on the context collector scores. The other electronicdevices also make this determination based on the context collectorsscores that have been provided. Determining which electronic device ofthe electronic devices included in context-sharing group 814 to elect asthe context collector includes user device 802 comparing its own contextcollector score to the context collector scores received from communaldevice 804, user device 806, and user device 808. The other electronicdevices also compare their own context collector score to the scoresthey have received. Then, based on the comparison, user device 802 (andthe other electronic devices participating in context-sharing group 814)identifies the highest context collector score and elects the electronicdevice with the highest context collector score as context collector.

Since communal device 804, user device 806, and user device 808 make theabove determination based on the same data and information as userdevice 802, they each also elect the same electronic device to becontext collector as user device 802. Thus, an electronic deviceparticipating in context-sharing group 814 will be aware of whether ornot it is elected as context collector based on its own contextcollector score comparison. However, in some examples, each electronicdevice participating in context-sharing group 814 transmits an electionindication to the other electronic devices that indicates the contextcollector that each electronic device elected.

In the examples described above where user device 802, communal device804, user device 806, and user device 808 each transmit a contextcollection indication, determining which electronic device of theelectronic devices participating in context-sharing group 814 to electas the context collect further includes user device 802 (and the otherelectronic devices participating in context-sharing group 814)determining whether or not context-sharing group 814 currently includesa context collector based on the received context collector indications.In these examples, if user device 802 determines that context-sharinggroup 814 already includes a context collector, then user device 802elects the existing context collector as context collector ofcontext-sharing group 814 regardless of the context collector scorecomparison outcome. If user device 802 determines that context-sharinggroup 814 already includes two or more context collectors, then userdevice 802 elects a context collector based on the determined contextcollector scores (as described above). This in turn improves thestability of the context collector, as it ensures that the contextcollector of context-sharing group 814 will not change unless theexisting context collector leaves context-sharing group 814.

Note, in the examples mentioned above in which context-sharing group 814includes more than one (e.g., two) context collectors, user device 802(and the other electronic devices participating in context-sharing group814) will elect a context collector based on a comparison of thedetermined context collector scores if the received context collectorindications indicate that context-sharing group 814 includes more thanthe allowable number of context collectors. For example, ifcontext-sharing group can include two context collectors and thereceived context collector indications indicate that there are currentlytwo context collectors participating in context-sharing group 814, thenuser device 802 will elect the two existing context collectorsregardless of the context collector score comparison outcome. However,if the received context collector indications indicate that there arecurrently three or more context collectors participating incontext-sharing group 814, then user device 802 will elect a contextcollector based on a comparison of the determined context collectorscores.

If, for example, user device 802 (and the other electronic devicesparticipating in context-sharing group 814) elect user device 802 ascontext collector of context-sharing group 814, user device 802 willestablish a communications connection with communal device 804, userdevice 806, and user device 808 (via network 810) so that user device802 may receive context information from one or more of those electronicdevices and transmit an aggregate context of context-sharing group(e.g., a stored collection of context information received from one ormore (e.g., each) electronic devices participating in context-sharinggroup 814) to one or more of those electronic devices (e.g., in responseto a received request for the aggregate context). Communal device 804,user device 806, and user device 808 will similarly establishcommunications connections with the other electronic deviceparticipating in context-sharing group 814 if one of those electronicdevices is elected as context collector.

As mentioned above, in some examples, electronic devices participatingin a context-sharing group automatically share context information witha context collector of a context-sharing group in response to undergoinga “device state change.” Examples of a device state change include mediaplayback, activation (e.g., opening) of a stored software application, atimer event (e.g., a timer of an electronic device going off), an alarmevent (e.g., an alarm of an electronic device going off), a change inpower state (e.g., an electronic device is turned on or off), a changein display visibility (e.g., a display of an electronic device isrepositioned from a display down position to a display up position (suchthat the display is visible to a user of the electronic device in thedisplay up position)), detection of a digital assistant trigger word orphrase (e.g., “Hey Siri,” “Siri,” or the like), initiation of a digitalassistant dialog session via the pressing or holding of a physicalbutton on a device, and an end of a digital assistant dialog session(e.g., after a digital assistant of an electronic deviceprovides/outputs a digital assistant response to a user request).

For example, as shown in FIG. 8, user device 808 undergoes a devicestate change once alarm event 820 begins. Thus, user device 808transmits context information associated with user device 808 to theelected context collector of context-sharing group 814 soon after (e.g.,immediately after or several seconds after (e.g., 0.5 seconds after, 1second after, or the like)) alarm event 820 begins. As represented byarrows 822 a, if user device 802 is elected as context collector, userdevice 808 transmits context information to user device 802.Alternatively, as represented by arrows 822 b, if communal device 804 iselected as context collector, user device 808 transmits contextinformation to communal device 804. In addition to transmitting thecontext information to the context collector (e.g., user device 802 orcommunal device 804), user device 808 transmits a device identification(also referred to as a device identifier) to the context collector(e.g., with the context information). In some examples, the deviceidentifier is predetermined (e.g., a predetermined serial number or thelike). In some examples, the device identifier is randomly generated byuser device 808 (e.g., a randomly generated number). In some examples,user device 808 is assigned a device identifier by the context collectorof context-sharing group 814 upon joining context-sharing group 814.

In response to receiving the device identifier, the context collectorstores an association between user device 808 and the device identifier.As will be described in greater detail below with reference to FIG. 9,the stored associations between electronic devices and their deviceidentifiers are used to transmit commands to specific electronicdevices. Specifically, in some examples, the context collector informsthe electronics devices participating in a context-sharing group of thestored associations so that each of the electronic devices is capable ofrelaying/transmitting commands (e.g., that are received from a remotedevice) to one or more other electronic devices based on the deviceidentifiers corresponding to the one or more other electronic devices.The context collector also associates the device identifiercorresponding to user device 808 with the context information receivedfrom user device 808 when adding the context information to the storedaggregate context of context-sharing group 814. In this manner, thecontext information included in the aggregate context may be organizedbased on its associated device identifier. As will be described ingreater detail below with reference to FIG. 9, one or more remotedevices (e.g., one or more servers) use the device identifiers includedin the aggregate context when selecting one or more electronic devicesto perform one or more tasks in response to a user request.

The context information transmitted by an electronic device (e.g., userdevice 808) in response to undergoing a device state change includesvarious types of context information associated with the electronicdevice. Examples of context information that an electronic devicetransmits in response to undergoing a device state change include devicestate change information (e.g., a state change type (e.g., timer event,alarm event, end of digital assistant dialog session, etc.), a statechange time, or the like), device capability information (e.g., type ofdevice, processing power, memory availability, display information(e.g., whether a device has a display and/or a size of the display),speaker information (e.g., whether a device has a speaker and/or aloudness of the speaker), and/or the like), and contextual stateinformation (e.g., device location (e.g., based on GPS data from GPSmodule 235 and/or information from a software application that hascontext-sharing group functionality (e.g., HomeKit®)), displayvisibility (e.g., display up or down), user attention information (e.g.,whether a user is currently looking at the device display (e.g., basedon information from an optical sensor 264 on the front and/or back of adevice)), strength of network connection (e.g., to network 810), amountof battery power, type of power source (e.g., battery vs wired powersource), and/or the like).

As discussed above, the elected context collector of context-sharinggroup 814 receives the above context information from one or moreelectronic device participating in context-sharing group 814 andsubsequently aggregates and stores that context information in anaggregate context. Further, the context collector updates the aggregatecontext as it receives additional context information from the one ormore electronic devices. For example, if user device 808 were to undergoanother device state change after alarm event 820, user device 808 wouldsend its most up-to-date/recent context information to the contextcollector of context-sharing group 814 so that the context collector mayincorporate new context information associated with user device 808 intothe aggregate context and/or remove outdated/previous contextinformation associated with user device 808 from the aggregate context(e.g., remove previous context information that is differentfrom/conflicts with newly-received context information).

In some examples, the context collector only stores the most recentcontext information received from each electronic device participatingin context-sharing group 814 (because the context collectorremoves/deletes previously-received context information associated witha device after receiving new context information associated with thesame device). In some examples, the context collector stores contextinformation associated with an electronic device for a predeterminedperiod of time (e.g., 1 hour, 1 day, 1 week, or the like) beforeremoving/deleting the context information. In some examples, the contextcollector stores context information associated with an electronicdevice from a predetermined number (e.g., 3, 5, 10, or the like) ofprevious context information transmissions. For example, the contextcollector may store context information from each electronic device'slast five context information transmissions. In some examples, thecontext collector stores a short history of events for each electronicdevice. In some examples, this short history is based on a type ofevent. For example, the context collector may store data correspondingto each electronic device's last three alarm events. In some examples,the context collector removes/deletes an electronic device's contextinformation when the electronic device leaves context-sharing group 814.

Then, as will be described in greater detail below with reference toFIGS. 9, 10, and 12A-13, the context collector transmits the aggregatecontext (or, at least a portion of the aggregate context) to one or moreelectronic devices participating in context-sharing group 814 inresponse to receiving a request for the aggregate context from the oneor more electronic devices. In some examples, transmitting the aggregatecontext to the one or more electronic devices causes the one or moreelectronic devices to obtain a digital assistant response to a userrequest based on the aggregate context (or, based on at least a portionof the aggregate context).

5. System and Technique for Task Performance in a Context-Sharing Group

FIG. 9 illustrates a system and technique for performing one or moretasks in a context-sharing group, according to various examples. System900 includes communal device 904, user device 906, communal device 908,and user device 910, all of which are participating in context-sharinggroup 914 (which is associated with a specific location (e.g., a home,an office, or the like)). User device 906 and user device 910 are bothclient devices (e.g., user devices 104, 122, 200, 400, or 600). Forexample, user device 906 and user device 910 are both an iPhone®. In theexamples described below, user device 906 is registered to user 902whereas user device 910 is not registered to user 902. Communal device904 is a smart speaker that has the same or similar digital assistantcapabilities as the user devices. Communal device 908 is a smart TV(connected display not shown) that has the same or similar digitalassistant capabilities as the user devices. Communal device 908 is thecontext collector of context-sharing group 914 (e.g., because communaldevice 908 was previously elected to be context collector). As discussedabove with reference to FIG. 8, communal devices are not registered to asingle user or are registered to multiple users (e.g., such that thecommunal device may be used by multiple users without additional userregistration and/or user authentication requirements). For example,communal device 904 is a HomePod® and communal device 910 is an AppleTV®.

System 900 further includes network 912 and server 916 (e.g., DA server106). Network 912 is a wireless communications network (e.g., network(s)110). As shown, communal device 904, user device 906, communal device908, and user device 910 communicate with one another and with server916 via network 912 (and thus are each connected to network 912).Further, server 916 is a remote device that is not participating incontext-sharing group 914. In some examples, system 900 includes one ormore other remote devices (e.g., a local server, a cloud-computingsystem, or the like) instead of server 916. It should be recognizedthat, in these examples, any of the operations performed by communaldevice 904, user device 906, communal device 908, and/or user device 910can instead be performed by server 916. For example, server 916 canperform the operations of the respective DA client modules (e.g., DAclient module 229) of communal device 904, user device 906, communaldevice 908, user device 806, and/or user device 910.

As shown in FIG. 9, user 902 provides user voice input 918 (e.g., “HeySiri, stop the timer.” or “Hey Siri, play music.”), which is received bycommunal device 904. User voice input 918 includes a digital assistanttrigger. A digital assistant trigger is a word or phrase that initiatesa dialog session with a digital assistant of an electronic device (e.g.,“Hey Siri,” “Siri,” of the like). Thus, after receiving user voice input918, communal device 904 detects the digital assistant trigger (e.g.,determines that user voice input 918 includes the digital assistanttrigger), determines that user voice input 918 represents a digitalassistant request (based on the detection of the digital assistanttrigger), and begins processing user voice input 918 to determine and/orobtain a response to user voice input 918 (e.g., the performance of oneor more tasks and/or the output of a digital assistant response).

Typically, it takes a communal device/user device less than 2 seconds(e.g., 1 second, 1.5 seconds, or the like) to begin processing a uservoice input as described above from when the communal device/user devicedetects the digital assistant trigger. During this time, the communaldevice/user device communicates (e.g., via a wireless network (e.g.,network 912) and/or a short distance communication connection (e.g.,Bluetooth, BTLE, or the like)) with one or more nearby electronicdevices (e.g., a second communal device/user device participating in thesame context-sharing group) that also received the user voice input anddetected the digital assistant trigger included in the user voice inputin order to determine which device should process the received uservoice input.

However, in some examples, a communal device/user device (e.g.,participating in a context-sharing group) that receives the user voiceinput takes longer than 2 seconds (e.g., 3 seconds, 5 seconds, or thelike) to detect the digital assistant trigger included in the voiceinput, and thus misses out on the opportunity to communicate with othernearby electronic devices that detected the digital assistant triggerwithin the two-second window and determine which device will respond tothe user voice input. As such, the communal device/user device with thedelayed digital assistant trigger detection will begin processing theuser voice input even if another communal device/user device (that didnot have a delayed digital assistant trigger detection) has alreadybegun processing the user voice input and/or has already provided aresponse to the user voice input. This in turn may result in multipledevices (participating in the same context-sharing group) providing aresponse to the same user voice input at different times, which mayresult in a poor user experience (e.g., due to user confusion and/orannoyance). For example, if user device 906 also receives user voiceinput 918 but detects the digital assistant trigger included therein 3seconds after communal device 904 detects the digital assistant trigger,user device 906 and communal device 904 may each end up providing aresponse to user voice input 918 (e.g., at different times).Accordingly, it can be desirable to suppress a communal device's and/oruser device's delayed digital assistant trigger detection.

FIG. 10 illustrates a system and technique for suppressing a delayeddigital assistant trigger detection using a context collector of acontext-sharing group, according to various examples. System 1000 issimilar to system 900. Specifically, system 1000 includes communaldevice 1004 (corresponding to communal device 904), user device 1006(corresponding to user device 906), and communal device 1008(corresponding to communal device 908), all of which are participatingin context-sharing group 1012 (corresponding to context-sharing group914). System 1000 further includes network 1010 (corresponding tonetwork 912). For simplicity, a user device corresponding to user device910 and a server corresponding to server 916 are not shown. As withsystem 900, communal device 1008 is the context collector ofcontext-sharing group 1012 in the examples described below (e.g.,because communal device 1008 was previously elected to be contextcollector).

It should be recognized that, in these examples, any of the operationsperformed by communal device 1004, user device 1006, and communal device1008 can instead be performed by one or more servers (e.g., a servercorresponding to with server 916) and/or one or more other remotedevices (e.g., a cloud-computing system). For example, one or moreservers can perform the operations of the respective DA client modules(e.g., DA client module 229) of communal device 1004, user device 1006,and/or communal device 1008.

As shown in FIG. 10, user 1002 provides user voice input 1014 (e.g.,corresponding to user voice input 918 (e.g., “Hey Siri, stop the timer.”or “Hey Siri, play music.”)) that includes a digital assistant trigger.User voice input 1014 is received by communal device 1004 and userdevice 1006 (e.g., because communal device 1004 and user device 1006 arelocated near one another (e.g., in the same room)). However, communaldevice 1004 detects the digital assistant trigger before user device1006. Thus, while user device is still determining whether user voiceinput 1014 includes a digital assistant trigger, communal device 1004initiates a digital assistant dialog session. Further, as represented byarrows 1016, communal device 1004 transmits contextual information (anda device identifier corresponding to communal device 1004) to communaldevice 1008 (because the detection of a digital assistant trigger is adevice state change and communal device 1008 is the context collector).For example, communal device 1004 transmits the contextual informationand device identifier in response to detecting the digital assistanttrigger.

Because the device state change of communal device 1004 was thedetection of a digital assistant trigger, the contextual informationtransmitted to communal device 1008 includes a trigger advertisement(e.g., along with other device state change information). The triggeradvertisement includes a digital assistant trigger end time, which is atime at which the digital assistant trigger ended according to communaldevice 1004 (e.g., a time at which communal device 1004 stoppedreceiving the audio signal corresponding to the digital assistanttrigger). In some examples, the trigger advertisement further includesdata indicating an energy level (e.g., a decibel level) of the digitalassistant trigger (e.g., the energy level of the audio signalcorresponding to the digital assistant trigger). In some examples, thefirst trigger advertisement further includes data indicating aconfidence score corresponding to a confidence of communal device 1004that user voice input 1014 includes a digital assistant trigger.

After receiving the context information and trigger advertisement fromcommunal device 1004, communal device 1008 updates the aggregate contextof context-sharing group 1012 to include the context information andtrigger advertisement. Further, as represented by arrows 1017, inresponse to receiving the trigger advertisement, communal device 1008retrieves and transmits trigger advertisements (associated with one ormore other electronic devices participating in the context-sharinggroup) that are already included in the aggregate context to communaldevice 1004 (e.g., trigger advertisements received within apredetermined period of time (e.g., within the last 30 seconds, withinthe last minute, within the last 5 minutes, or the like)). In someexamples, communal device 1008 transmits the aggregate context(including the received trigger advertisements) to communal device 1004instead of only transmitting the trigger advertisements. As will bedescribed in greater detail below with respect to user device 1006,communal device 1004 uses the trigger advertisements received fromcommunal device 1008 (e.g., the data included in the triggeradvertisements) to determine whether it should suppress its own digitalassistant trigger detection (and thus forgo further processing of uservoice input 1014).

However, in this case, communal device 1004 does not suppress thedetection of the digital assistant trigger (e.g., because communaldevice 1004 is the first electronic device to detect the digitalassistant trigger included in user voice input 1014) and continuesprocessing user voice input 1014 (e.g., to determine/obtain a responseto user voice input 1014 (e.g., the performance of one or more tasksand/or the output of a digital assistant response)). Thus, asrepresented by arrows 1018, communal device 1004 transmits a request forthe aggregate context of context-sharing group 1012 to communal device1008. As represented by arrows 1020, in response to receiving therequest for the aggregate context, communal device 1008 transmits theaggregate context to communal device 1004. In some of the examplesmentioned above where communal device 1008 transmits the aggregatecontext at arrows 1017 instead of only transmitting the triggeradvertisements, arrows 1018 and 1020 do not occur because communaldevice had already received the aggregate context. After communal device1004 receives the aggregate context (as represented by arrows 1020 or,in some examples, arrows 1017) and determines that it should continueprocessing user voice input 1014, communal device 1004 obtains aresponse to user voice input 1014 based on user voice input 1014 andcontext information included in the aggregate context (as will bedescribed in greater detail below with reference to FIG. 9).

As represented by arrows 1022, in response to detecting the digitalassistant trigger included in user voice input 1014, user device 1006transmits context information (and a device identifier corresponding touser device 1006) to communal device 1008 (because the detection of adigital assistant trigger is a device state change and communal device1008 is the context collector). Note, while FIG. 10 illustrates userdevice 1006 transmitting the context information to communal device 1008after arrows 1020, user device 1006 transmits the context information atany time after communal device 1004 detects the digital assistanttrigger and transmits context information to communal device 1008 (asrepresented by arrows 1016). For example, User device 1006 may transmitcontext information to communal device 1008 before communal device 1004receives the aggregate context from communal device 1008 (ad representedby arrows 1020). As discussed above, because the device state change ofuser device 1006 was the detection of a digital assistant trigger, thecontextual information transmitted to communal device 1008 includes atrigger advertisement corresponding to the digital assistant triggerdetection of user device 1006. The trigger advertisement transmitted byuser device 1006 includes the same type of data and information that isincluded in the trigger advertisement previously transmitted by communaldevice 1004 (e.g., data indicating a time at which the digital assistanttrigger ended (e.g., a time at which user device 1006 stopped receivingthe audio signal corresponding to the digital assistant trigger)).

After receiving the context information and trigger advertisement fromuser device 1006, communal device 1008 updates the aggregate context ofcontext-sharing group 1012 to include the context information andtrigger advertisement. Further, as represented by arrows 1024, inresponse to receiving the trigger advertisement from user device 1006,communal device 1008 retrieves and transmits trigger advertisements(associated with one or more other electronic devices participating inthe context-sharing group, including communal device 1004) that arealready included in the aggregate context to user device 1006 (e.g.,trigger advertisements received within a predetermined period of time(e.g., within the last 30 seconds, within the last minute, within thelast 5 minutes, or the like)). In some examples, communal device 1008transmits the aggregate context (including the received triggeradvertisements) to user device 1006 instead of only transmitting thetrigger advertisements.

In some examples, in addition to transmitting the context informationand trigger advertisement to communal device 1008 (via network 1010),user device 1006 transmits the trigger advertisement (e.g., datacorresponding to the trigger advertisement) to one or more electronicdevices with which user device 1006 shares a short distancecommunications connection (e.g., Bluetooth, BTLE, or the like). Forexample, if user device 1006 and communal device 1004 share a BTLEconnection, user device 1006 will transmit the trigger advertisementdirectly to communal device 1004 via the BTLE connection (e.g., beforeor soon after transmitting the context information and triggeradvertisement to communal device 1008). Then, in response to receivingthe trigger advertisement from user device 1006, the one or moreelectronic devices transmit their own trigger advertisements to userdevice 1006 via their respective short distance communicationsconnections. For example, the one or more electronic devices transmittrigger advertisements corresponding to digital assistant triggers thatthey have detected within a predetermined period of time (e.g., withinthe last 5 seconds, within the last 30 seconds, within the last minute,or the like)).

After receiving the trigger advertisements from communal device 1008(and, in some examples, from one or more electronic devices with whichuser device 1006 shares a short distance communications connection) userdevice 1006 determines whether it should suppress its own digitalassistant trigger detection (and thus forgo further processing of uservoice input 1014). Specifically, user device 1006 determines whether ornot each trigger advertisement it has received (e.g., within the lastsecond) is “sane” based on the digital assistant trigger end time (i.e.,the time at which a digital assistant trigger ends according to anelectronic device) included in each trigger advertisement. A triggeradvertisement is sane if its digital assistant trigger end time fallswithin a predetermined time range (e.g., 750 milliseconds, 500milliseconds, 100 milliseconds, or the like) before the digitalassistant trigger end time of user device 1006 (i.e., the time at whichthe digital assistant trigger included in user voice input 1014 endedaccording to user device 1006).

If user device 1006 determines that one or more of the triggeradvertisements it has received is sane (i.e., includes a digitalassistant trigger end time that falls within the predetermined timerange before the digital assistant trigger end time of user device1006), then user device 1006 forgoes further processing of user voiceinput 1014. For example, if user device 1006 determines that a triggeradvertisement corresponding to communal device 1004 (e.g., a triggeradvertisement received from communal device 1008 and/or received fromcommunal device 1004) is sane, then user device forgoes furtherprocessing of user voice input 1014 so that communal device 1004 will bethe only electronic device to provide a response to user voice input1014. However, in some examples, communal device 1004 receives one ormore sane trigger advertisements corresponding to one or more otherelectronic devices that detected the digital assistant trigger (e.g.,from communal device 1008 (e.g., as represented by arrows 1017)) andthus also forgoes further processing of user voice input 1014 (e.g.,instead of transmitting a request for the aggregate context to communaldevice 1008 (e.g., as represented by arrows 1018)).

If user device 1006 determines that none of the trigger advertisementsit has received is sane (i.e., none of the trigger advertisementsinclude a digital assistant trigger end time that falls within thepredetermined time range before the digital assistant trigger end timeof user device 1006), then user device 1006 continues processing uservoice input 1014 (e.g., by transmitting a request for the aggregatecontext to communal device 1008). Such a scenario would occur, forexample, if (1) the trigger advertisement of user device 1006corresponded to a digital assistant trigger detected 30 seconds aftercommunal device 1004 detected the digital assistant trigger included inuser voice input 1014 and (2) the predetermined time range was 500milliseconds before the digital assistant trigger end time correspondingto the digital assistant trigger detected by user device 1006. In thisexample, the digital assistant trigger end time of communal device 1004clearly does not fall within the 500-millisecond time range before thedigital assistant trigger end time of user device 1006. Thus, the uservoice input received by user device 1006 represents a separate userrequest (e.g., separate from the user request of user voice input 1014)that user device 1006 should continue processing.

Returning to FIG. 9, in some examples, user voice input 918 does notinclude a digital assistant trigger. For example, communal device 904may receive user voice input 918 during a digital assistant dialogsession initiated in response to user 902 pressing or holding a physicalbutton on communal device 904. In these examples, communal device 904determines that user voice input 918 represents a digital assistantrequest and begins processing user voice input 918 (e.g., as representedby arrows 920) to determine and/or obtain a response to user voice input918 without having to determine whether it should suppress the detectionof a digital assistant trigger (e.g., according to the process describedabove with reference to FIG. 10). Note, in these examples, theinitiation of the digital assistant dialog session via the pressing orholding of a physical button on communal device 904 represents a devicestate change and thus communal device 904 transmits context information(and a device identifier corresponding to communal device 904) tocommunal device 908 in response to initiating the dialog session.

As represented by arrows 920, in response to receiving user voice input918 (or, in some examples, in response to detecting the digitalassistant trigger included in user voice input 918), communal device 904transmits a request (via network 912) to communal device 908 (i.e., thecontext collector of context-sharing group 914) for communal device 908to transmit an aggregate context of context-sharing group 914 tocommunal device 904. Because the detection of a digital assistanttrigger is a device state change, communal device 904 also transmitscontext information (and a device identifier corresponding to communaldevice 904) to communal device 908 before transmitting the request forthe aggregate context (although this step is not shown in FIG. 9).

As represented by arrows 922, after receiving the request for theaggregate context from communal device 904, communal device 908transmits the aggregate context (or, in some examples, at least aportion of the aggregate context) to communal device 904. In someexamples, the request for the aggregate context causes communal device908 to transmit the aggregate context (e.g., data corresponding to theaggregate context), or at least a portion of the aggregate context, tocommunal device 904. The aggregate context transmitted to communaldevice 904 includes context information (e.g., device state changeinformation, contextual state information, device capabilityinformation, and/or the like) associated with at least communal device904, user device 906, and user device 910 (e.g., because communal device904, user device 906, and user device 910 each recently transmittedcontext information to communal device 908 in response to undergoing adevice state change (e.g., a timer event)). Specifically, the contextinformation is associated with at least communal device 904, user device906, and user device 910 based on the device identifiers that communaldevice 908 receives with the context information from at least communaldevice 904, user device 906, and user device 910. In some examples, theaggregate context does not include any other type of deviceidentification or identifying information other than the deviceidentifiers received with context information included in the aggregatecontext. This in turn helps ensure the anonymity of the electronicdevices participating in context-sharing group 914 when server 916receives the aggregate context (e.g., as represented by arrows 924).

In other examples, the aggregate context does include other types ofdevice identifications and/or information identifying a registered userof each electronic device (in addition to the device identifiers). Thisin turn allows server 916 to determine whether electronic devicesparticipating in a context-sharing group are registered to a single useror two or more different users (as this information may influence thecommands that server 916 provides). In some examples, deviceidentifications and/or information identifying a registered user of eachelectronic device included in the aggregate context allows server 916 todetermine whether or not a user voice input is provided by a registered.Further, as will be described below, in some examples, server 916 usesthis additional identifying information to access and/or utilize userdata that is stored on server 916 and that is associated with one ormore of the electronic devices (e.g., user data that an electronicdevice participating in the context-sharing group 914 previouslysynced/transmitted to the remote devices (e.g., during an automaticand/or periodic user data sync)).

As represented by arrows 924, after receiving the aggregate context fromcommunal device 908, communal device 904 provides (e.g., transmits) datacorresponding to user voice input 918 and at least a portion of theaggregate context to server 916.

In some examples, communal device 904 provides audio data correspondingto user voice input 918 to server 916. In some examples, communal device904 performs speech-to-text processing of user voice input 918 (e.g.,using STT processing module 730) and provides text data corresponding touser voice input 918 (e.g., a textual representation of user voice input918) to server 916. In some examples, communal device 904 furtherperforms natural language processing of the text data corresponding touser voice input 918 (e.g., using natural language processing module732) and provides results of the natural language processing (e.g., oneor more user intents) to server 916.

In some examples, communal device 904 provides all of the aggregatecontext to server 916. In some examples, communal device 904 determineswhat context information included in the aggregate context is relevantto user voice input 918 (e.g., when communal device 904 performs naturallanguage processing of user voice input 918) and only provides therelevant context information to server 916. In some examples, communaldevice 904 determines what context information is relevant based on oneor more domains of an active ontology (e.g., ontology 760) thatcorrespond to user voice input 918 (e.g., by identifying the contextinformation that is related to or associated with the one or moredomains corresponding to user voice input 918). In some examples,communal device 904 removes personal information (e.g., email addresses,home addresses, payment information, or the like) and/or user data(e.g., a user's preferences, media, contacts, speech profiles, or thelike) included in the aggregate context prior to providing the aggregatecontext to server 916. In some examples, communal device 904 encryptspersonal information and/or user data included in the aggregate contextprior to providing the aggregate context to server 916.

In some examples, prior to transmitting the at least a portion of theaggregate context to server 916, communal device 904 transmits a requestto each electronic device participating in context-sharing group 914(including user device 906, communal device 908, and user device 910)for each electronic device to provide communal device 904 with anindication of whether or not it detected the digital assistant triggerincluded in user voice input 918. In some examples, communal device 904requests each electronic device to provide communal device 904 with anindication of whether the electronic device has detected a digitalassistant trigger within a predetermined period of time (e.g., withinthe last 2 seconds, 5 seconds, or 10 seconds). In response to receivingthe request, the electronic devices transmit the requested indications(also referred to as trigger indications) with their respective deviceidentifier.

After receiving a trigger indication from one or more (e.g., all) of theelectronic devices participating in context-sharing group 914(indicating whether each of the one or more electronic devices did ordid not detect the digital assistant trigger included in user voiceinput 918), communal device 904 incorporates the trigger indicationsinto the aggregate context based on the device identifiers received withthe trigger indications. Specifically, communal device 904 incorporatesthe trigger indication received from each electronic device into thecontext information of the electronic device that is included in the atleast a portion of the aggregate context (according to the deviceidentifier of each electronic device). For example, communal device 904would incorporate a trigger indication received from user device 906into the context information associated with the device identifier ofuser device 906 that is included in the at least a portion of theaggregate context. In some examples, a trigger indication includes dataindicating an energy level (e.g., decibel level) of the detected digitalassistant trigger (e.g., the energy level of the digital assistanttrigger when received by an electronic device). In some examples, atrigger indication includes a confidence score corresponding to aconfidence of an electronic device (e.g., user device 906) that uservoice input 918 includes a digital assistant trigger.

Note, in some examples, user devices participating in a context-sharinggroup are not aware of other user devices that are also participating inthe context-sharing group (and that are not a context collector). Forexample, user device 906 is not aware of user device 910. Thus, in theseexamples, user devices cannot transmit trigger indication requests ortrigger indications directly to other user devices. Accordingly, inthese examples, user devices transmit trigger indication requests to thecontext collector of a context-sharing group so that thecontext-collector may transmit the trigger indication requests to allother electronic devices participating in the context-sharing group.Then, the context collector transmits all trigger indications itreceives back to the user devices that transmitted the triggerindication requests to the context collector. For example, in order toreceive a trigger indication from user device 910, user device 906transmits a trigger indication request to communal device 908 so thatcommunal device 908 may transmit the trigger indication request to bothuser device 910 and communal device 904. As a result, communal devicewill receive trigger indications from communal device 904 and userdevice 910, and subsequently transmit those trigger indications (alongwith its own trigger indication) to user device 906. In some examples,user device 906 transmits the trigger indication request directly tocommunal device 904 (e.g., in addition to transmitting the request tocommunal device 908), as user device 906 is still aware of communaldevices participating in context-sharing group 914.

As will be described in greater detail below, in some examples, server916 determines a physical proximity of user device 906, communal device908, and/or user device 910 to communal device 904 (e.g., within thespecific location associated with context-sharing group 914) based ontrigger indications corresponding to user device 906, communal device908, and/or user device 910 that are included in the aggregate context.For example, based on the trigger indications (e.g., data included inthe trigger indications), server 916 can determine whether user device906 or communal device 908 is closer to communal device 904 and/ordetermine whether user device 906 or communal device 908 is within asame area of the location associated with context-sharing group 914 ascommunal device 904 (e.g., within a same room or office). In someexamples, each individual device determines its own physical proximityto communal device 904. In these examples, a trigger indication includesdata indicating a physical proximity of the associated electronic device(e.g., user device 906, communal device 908, or user device 910) tocommunal device 904, and thus server 916 is informed of the proximity ofeach device to communal device 904 based on the data included in thetrigger indication (instead of server 916 determining the physicalproximity of each device to communal device 904).

As will be described in greater detail below with reference to FIG. 11,upon receiving the data corresponding to user voice input 918, server916 (specifically, one or more modules of server 916) processes the datacorresponding to user voice input 918 (e.g., based on contextinformation included in the aggregate context) and determines one ormore user intents corresponding to user voice input 918, one or moretasks corresponding to the one or more user intents, one or moreelectronic devices participating in context-sharing group 914 to performthe one or more tasks, and one or more commands to perform the one ormore tasks. Note, in some examples, communal device 904 does nottransmit the data corresponding to user voice input 918 and aggregatecontext to server 916. In these examples, communal device 904(specifically, one or more modules of communal device) processes thedata corresponding to user voice input 918 (e.g., based on contextinformation included in the aggregate context) and performs thedeterminations listed above (instead of server 916).

FIG. 11 is a block diagram illustrating a system for task determinationand device selection in a context-sharing group, according to variousexamples. System 1100 is implemented on one or more remote devices thatare communicatively connected (e.g., via one or more networks (e.g.,network 912)) to one or more electronic devices (e.g., one or more userdevices and/or one or more communal devices) that are participating in acontext-sharing group (e.g., context-sharing group 914). For example,system 1100 is implemented on server 916. In some examples, system 1100is implemented one or more electronic devices that are participating ina context-sharing group (e.g., communal device 904, user device 906,communal device 908, and/or user device 910). In some examples, themodules and functions of system 1100 are distributed between one or moreremote devices and one or more electronic devices that a participatingin a context-sharing group.

System 1100 is implemented using hardware, software, or a combination ofhardware and software to carry out the functions discussed herein.Further, system 1100 is exemplary, and thus system 1100 can have more orfewer components than shown, can combine two or more components, or canhave a different configuration or arrangement of the components.Although the below discussion describes functions being performed at asingle module of system 1100, it is to be understood that such functionscan be performed at other modules of system 1100 and that such functionscan be performed at more than one module of system 1100.

To illustrate the examples discussed herein, system 1100 is describedwith reference to FIG. 9 and the various components of system 900.Unless otherwise stated, system 1100 is implemented on server 916 in theexamples described below.

System 1100 includes voice input receiver module 1102. Voice inputreceiver module 1102 receives data corresponding to a user voice input(e.g., audio data, text data, natural language processing results,and/or the like) from an electronic device participating in acontext-sharing group (e.g., from communal device 904). For example,voice input receiver module 1102 receives data corresponding to uservoice input 918 from communal device 904 (e.g., as represented by arrows924). In some examples, voice input receiver module 1102 receives a uservoice input directly from a user. For example, voice input receivermodule 1102 receives user voice input 918 directly from user 902 whensystem 1100, or just voice input receiver module 1102, is implemented oncommunal device 904 (as communal device 904 receives user voice input918 from user 902). After voice input receiver module 1102 receives datacorresponding to a user voice input, voice input receiver module 1102provides the data corresponding to the user voice input to user intentmodule 1106.

System 1100 includes aggregate context receiver module 1104. Aggregatecontext receiver module 1104 receives at least a portion of an aggregatecontext of a context-sharing group from an electronic deviceparticipating in a context-sharing group (e.g., from communal device904). As described above, the at least a portion of the aggregatecontext includes one or more device identifiers corresponding to one ormore electronic devices participating in the context-sharing group. Forexample, aggregate context receiver module 1104 receives at least aportion of an aggregate context of context-sharing group 914 fromcommunal device 904 (e.g., as represented by arrows 924). In someexamples, aggregate context receiver module 1104 receives the at least aportion of the aggregate context from a context collector of acontext-sharing group. For example, aggregate context receiver module1104 receives the at least a portion of the aggregate context fromcommunal device 908 (the context collector of context-sharing group 914)when system 1100, or just aggregate context receiver module 1104, isimplemented on communal device 904 (as communal device 904 receives theat least a portion of the aggregate context from communal device 908(e.g., as represented by arrows 922)). After receiving the at least aportion of the aggregate context of a context-sharing group, aggregatecontext receiver module 1104 provides context information (e.g., devicestate change information, contextual state information, and/or devicecapability information) and device identifiers associated with thecontext information to user intent module 1106, device selection module1110, and/or command module 1112.

System 1100 includes user intent module 1106. User intent module 1106determines one or more user intents based on data corresponding to auser voice input (received from voice input receiver module 1102). Forexample, user intent module 1106 determines one or more user intentsbased on the data corresponding to user voice input 918. Afterdetermining one or more user intents, user intent module 1106 providesthe one or more user intents to task determination module 1108.

In some examples, determining the one or more user intents includes userintent module 1106 performing speech-to-text processing, naturallanguage processing, and/or the like based on the data corresponding tothe user voice input. In these examples, user intent module 1106includes a speech-to-text processing module (e.g., STT processing module730), a natural language processing module (e.g., natural languageprocessing module 732), and/or the like. For example, if the datacorresponding to user voice input 918 is audio data (e.g., an audiosignal of user voice input 918), determining the one or more userintents includes user intent module 1106 performing speech-to-textprocessing based on the audio data. As another example, if the datacorresponding to user voice input 918 is text data (e.g., a textualrepresentation of user voice input 918), determining the one or moreuser intents includes user intent module 1106 performing naturallanguage processing based on the text data (but not speech-to-textprocessing, as user voice input 918 has already been recognized (e.g.,by communal device 904)).

In some of the examples where user intent module 1106 performsspeech-to-text processing of the data corresponding to user voice input,user intent module 1106 determines one or more recognition results(e.g., one or more candidate text representations) corresponding to theuser voice input based on user data (e.g., stored contacts, user speechprofiles, media (e.g., songs), and/or the like) that is associated witha user that provided the user voice input. For example, if user voiceinput 918 includes a unique and/or uncommon word and/or name (e.g., “HeySiri, call Daenerys Targaryen.”), user intent module 1106 can utilizespeech profile data associated with user 902 (e.g., speech profile dataassociated with stored contacts of user 902) to recognize the uniqueand/or uncommon word and/or name. For example, user intent module 1106can match the utterance of “Daenerys Targaryen” included in user voiceinput 918 (e.g., an audio signal or intermediate recognition resultcorresponding to the utterance) to an utterance of the stored contactname “Daenerys Targaryen” included in a user speech profile of user 902.

In some examples, the user data utilized by user intent module 1106includes user data that is stored on the electronic device that providesthe data corresponding to the user voice input to voice input receivermodule 1102 (e.g., communal device 904). For example, communal device904 may transmit stored user data to server 916 when transmitting thedata corresponding to user voice input 918 to server 916 (e.g., the userdata may be included in the aggregate context). The user data may thenbe accessed and utilized by user intent module 1106. In some examples,the user data utilized by user intent module 1106 includes user datathat is stored on the remote device that is implementing user intentmodule 1106 (e.g., server 916). For example, the user data may alreadybe stored on server 916 because communal device 904 previouslysynced/transmitted the user data to server 916 (e.g., during anautomatic and/or periodic user data sync).

In some examples, the user data utilized by user intent module 1106includes user data associated with an electronic device that (1) isparticipating in a context sharing group and (2) does not provide thedata corresponding to the user voice input to voice input receivermodule 1102. For example, the user data that user intent module 1106utilizes when performing speech-to-text processing of the datacorresponding to user voice input 918 can include user data that userdevice 906 previously synced/transmitted to server 916. For example, ifuser voice input 918 includes the unique name “Daenerys Targaryen,” userintent module 1106 can recognize the unique name based on speech profiledata associated with user 902 that user device 906 previouslysynced/transmitted to server 916. In this example, the user dataassociated with user device 906 is not stored on communal device 904 andhas not been synced/transmitted to server 916 by communal device 904.

In some examples, an electronic device participating in context-sharinggroup that does not provide data corresponding to a user voice input tovoice input receiver module 1102 (e.g., user device 906, communal device908, or user device 910)) must be registered to the user that providesthe user voice input (e.g., user 902) in order for user intent module1106 to utilize user data associated with the electronic device. Forexample, if user device 906 is not registered to user 902, user intentmodule 1106 will not be able to utilize user data associated with userdevice 906 to recognize the unique name “Daenerys Targaryen” included inuser voice input 918. In some examples, user intent module 1106 utilizesuser data from an electronic device registered to the user that providesthe user voice input only if the electronic device is participating inthe same context-sharing group as the electronic device that receivesthe user voice input. For example, if an electronic device registered touser 902 is not participating in context-sharing group 914, then userintent module 1106 cannot access user data associated with thatelectronic device when processing the data corresponding to user voiceinput 918. As another example, if user device 906 is registered to user902, but user device 906 leaves context-sharing group 914 (e.g., bydisconnecting from network 912) before user intent module 1106 receivesthe data corresponding to user voice input 918, then user intent module1106 will not be able to utilize user data associated with user device906 (e.g., that is stored on server 916) to recognize user voice input918. Note, in some examples, communal devices (e.g., communal device904) do not store user data and/or do not sync user data to remotedevices (e.g., server 916). In these examples, user intent module 1106can only access and utilize user data associated with user devices(e.g., user device 906 and/or user device 910) that are registered tothe user that provides the user voice input.

As mentioned above, aggregate context receiver module 1104 providescontext information (e.g., device state change information, contextualstate information, and/or device capability information) and deviceidentifiers associated with the context information to user intentmodule 1106. In some examples, user intent module 1106 determines theone or more user intents further based on context information(associated with one or more electronic devices) received from aggregatecontext receiver module 1104.

In some examples, determining the one or more user intents further basedon context information included in the at least apportion of theaggregate context includes user intent module 1106 disambiguating a uservoice input based on the context information. For example, if user voiceinput 918 is ambiguous with respect to a user-requested task (e.g., “HeySiri, stop.” is ambiguous with respect to what task user 902 wants adevice to perform as it is unclear whether user 902 wants to stop mediaplayback, stop an alarm, stop a timer, or the like)), user intent module1106 can use device state change information associated with communaldevice 904, user device 906, communal device 908, and/or user device 910(e.g., a type of device state change and/or a time of device statechange) to determine/disambiguate what task user 902 is referring to inuser voice input 918. For example, if device state change informationassociated with user device 906 (e.g., data indicating a type of devicestate change at user device 906) indicates that there is a timer eventcurrently occurring at user device 906 (e.g., a timer is going off atuser device 906), user intent module 1106 may determine that user 902wants to stop the timer event at user device 906. Thus, in this example,user intent module 1106 would determine a user intent of stopping atimer.

In some examples, when a user voice input is ambiguous with respect to auser-requested task, and two or more events (e.g., timer event, alarmevent, media playback, and/or the like) are occurring at two or moreseparate electronic devices in a context-sharing group, user intentmodule 1106 uses device state change time information (e.g., dataindicating a time when each event began) to determine the one or moreuser intents based on the most recent device state change. For example,if in the example above (where user voice input 918 is “Hey Siri,stop.”), the device state change information also indicates that thereis a media playback event occurring at communal device 904 (e.g.,communal device 904 is currently playing music while a timer is goingoff at user device 906 (e.g., in another room)), user intent module 1106can disambiguate user voice input 918 based on device state change timeinformation indicating a time when each event began. Specifically, userintent module 1106 can determine which event began most recently basedon the device state change time data, as that it the event user 902 ismost likely referring to. Thus, if the timer event at user device 906began more recently than the media playback event at communal device904, user intent module 1106 would determine a user intent of stopping atimer instead of a user intent of stopping media playback.

In some examples, when a user voice input is ambiguous with respect to auser-requested task, and two or more events (e.g., timer event, alarmevent, media playback, and/or the like) are occurring at two or moreseparate electronic devices in a context-sharing group, user intentmodule 1106 uses device state change type information (e.g., dataindicating a type of event) to determine the one or more user intentsbased on the type of events occurring at the two or more separateelectronic devices. Specifically, in these examples, user intent module1106 determines the one or more user intents based on event priorityrules that indicate which event types are given preference whendetermining a user intent. For example, the event type priority rulesmay indicate that alarm events are prioritized over media playbackevents. Thus, if in the example above (where user voice input 918 is“Hey Siri, stop.”), the device state change information also indicatesthat there is a media playback event occurring at communal device 904(e.g., communal device 904 is currently playing music while a timer isgoing off at user device 906 (e.g., in another room)), user intentmodule 1106 can disambiguate user voice input 918 based on the eventpriority rules and thus determine a user intent of stopping a timerinstead of a user intent of stopping media playback (as timer events areprioritized over media playback events).

Similarly, in yet another example, if user voice input 918 is “Hey Siri,resume” and device state change information included in the at least aportion of the aggregate context indicates that music previously playingat user device 906 was stopped 10 minutes ago whereas a movie playing atcommunal device 908 was stopped 5 minutes ago (because stopping orpausing a media playback is a device state change), user intent module1106 would determine, based on the device state change time data, thatthe movie playing at communal device 908 was stopped or paused morerecently. Thus, user intent module 1106 would determine a user intent ofresuming a movie instead of a user intent of resuming music.

As will be described in greater detail below with reference to FIG. 13,in some examples, user intent module 1106 uses one or more digitalassistant dialog session histories associated with one or moreelectronic devices (included in the aggregate context) to disambiguate auser voice input and determine one or more user intents corresponding tothe user voice input.

System 1100 includes task determination module 1108. Task determinationmodule 1108 determines one or more tasks to be performed by one or moreelectronic devices that are participating in a context-sharing groupbased on one or more user intents received from user intent module 1106.For example, task determination module 1108 determines one or more tasksto be performed by communal device 904, user device 906, communal device908, and/or user device 910 based on one or more user intents that userintent module 1106 determines based on data corresponding to user voiceinput 918 received by voice input receiver module 1102 (and, in someexamples, further based on context information included in the aggregatecontext received by aggregate context receiver module 1104). Afterdetermining one or more tasks, task determination module 1108 providesthe one or more tasks and the one or more user intents to deviceselection module 1110.

As will be described in greater detail below, the one or more tasks areperformed by one or more electronic devices participating in acontext-sharing group to fulfill the one or more user intents. Forexample, if user intent module 1106 determines a user intent of stoppingan alarm (e.g., based on the user voice input “Hey Siri, stop.” or “HeySiri, stop the alarm.”), task determination module 1108 will determineone or more tasks that, when performed by an electronic device, wouldresult in the electronic device stopping an alarm. In some examples, theone or more tasks that task determination module 1108 determines arepredetermined based on the one or more user intents (e.g., a determineduser intent corresponds to one or more tasks). Examples of the one ormore tasks that can be determined by task determination module 1108include performing a search, retrieving information/data, opening anapplication stored on an electronic device, playing media (e.g., songs,videos, movies, and/or the like), making a purchase, userauthentication, displaying retrieved information/data, and/or the like.

As will be described in greater detail below with reference to FIG. 13,in some examples, task determination module 1108 uses one or moredigital assistant dialog session histories associated with one or moreelectronic devices to disambiguate a user voice input and determine oneor more parameters for one or more tasks determined based on the userintent corresponding to the user voice input.

System 1100 includes device selection module 1110. Device selectionmodule 1110 selects/identifies one or more electronic devicesparticipating in a context-sharing group to perform one or more tasks(received from task determination module 1108) based at least on contextinformation included in the aggregate context (received from aggregatecontext receiver module 1104). For example, device selection module 1110can select one electronic device that is participating incontext-sharing group 914 (e.g., user device 906) to perform the one ormore tasks. As another example, as will be discussed in greater detailbelow with reference to FIGS. 12A-12B, device selection module 1110 canselect two or more electronic devices that are participating incontext-sharing group 914 (e.g., communal device 904 and user device906) to perform at least one task each (e.g., when task determinationmodule 1108 determines at least two tasks). In some examples, deviceselection module 1110 selects the electronic device that provides thedata corresponding to a user voice input to voice input receiver module1102 (e.g., communal device 904). In some examples, device selectionmodule 1110 selects an electronic device that does not provide the datacorresponding to a user voice input to voice input receiver module 1102(e.g., user device 906, communal device 908, and/or user device 910). Insome examples, device selection module 1110 selects a context collectorof a context-sharing group (e.g., communal device 908).

After receiving the one or more tasks, the one or more user intents, andthe aggregate context, device selection module 1110 determines, based ondevice state change information included in the aggregate context (e.g.,device state change information associated with one or more electronicdevices participating in a context-sharing group), whether an event(e.g., a timer event, an alarm event, media playback, or the like) thatcorresponds to a user intent of the one or more user intents iscurrently occurring at one or more electronic devices participating in acontext sharing group. For example, if device selection module 1110receives a user intent of stopping a timer (e.g., based on the uservoice input “Hey Siri, stop.”), user intent module 1110 will determinewhether there is a timer event occurring at one or more electronicdevices based on the device state change information (e.g., dataindicating a type of device state change) associated with the electronicdevices (e.g., associated with the device identifier of the one or moreelectronic devices included in the aggregate context). As anotherexample, if device selection module 1110 receives a user intent ofplaying a next song (e.g., based on the user voice input “Hey Siri, playthe next song.”), device selection module 1110 will determine whetherthere is a music playback event occurring at one or more electronicdevices based on the device state change information associated with theelectronic devices.

If device selection module 1110 determines that an event thatcorresponds to the user intent is currently occurring at a singleelectronic device participating in the context-sharing group, deviceselection module 1110 selects the single electronic device (at which theevent is occurring) to perform the one or more tasks.

If device selection module 1110 determines that an event thatcorresponds to the user intent is currently occurring at two or moreelectronic devices participating in the context-sharing group, deviceselection module 1110 determines which event (of the two or more events)began most recently based on data indicating a time of device statechange included in device state change information associated with thetwo or more electronic devices. For example, if device selection module1110 receives a user intent of stopping an alarm (e.g., based on theuser voice input “Hey Siri, stop.”) and device selection module 1110determines that an alarm event is occurring at user device 906 and userdevice 910 (i.e., a separate alarm is going off at each device), thendevice selection module 1110 will determine whether the alarm event atuser device 906 began more recently than the alarm event at user device910 (based on the device state change data indicating a time at whicheach alarm event began). Then, after device selection module 1110determines which event (of the two or more events) began most recently,device selection module 1110 selects the electronic device at which theevent began most recently to perform the one or more tasks. Returning tothe previous example, if device selection module 1110 determines thatthe alarm event at user device 910 began more recently than the alarmevent at user device 906 (e.g., the alarm at user device 910 startedgoing off when the alarm at user device 906 was already going off),device selection module 1110 will select user device 910 (specifically,device selection module 1110 will select the device identifiercorresponding to user device 910).

In some examples, if device selection module 1110 determines that anevent that corresponds to the user intent is currently occurring at twoor more electronic devices participating in the context-sharing group,device selection module 1110 determines, based on proximity informationincluded in the aggregate context, which electronic device of the two ormore electronic devices is physically closest to the electronic devicethat provided the user voice input data to voice input receiver module1102. Then, device selection module 1110 selects the electronic devicethat is physically closest to the electronic device that provided theuser voice input data. For example, if device selection module 1110receives a user intent of stopping an alarm (e.g., based on the uservoice input “Hey Siri, stop.”) and device selection module 1110determines that an alarm event is occurring at user device 906 and userdevice 910 (i.e., a separate alarm is going off at each device), deviceselection module 1110 will determine (based on proximity informationassociated with user device 906 and user device 910) whether user device906 or user device 910 is physically closest to communal device 904.Then, if device selection module 1110 determines that user device 906 isphysically closest to communal device 904, device selection module 1110will select user device 906.

In some examples, device selection module 1110 determines, based ondevice state change information included in the aggregate context (e.g.,device state change information associated with one or more electronicdevices participating in a context-sharing group), whether an event thatcorresponds to a user intent of the one or more user intents previouslyoccurred at one or more electronic devices (participating in a contextsharing group) within a predetermined period of time (e.g., within thelast 5 minutes, 10 minutes, 30 minutes, or the like). For example, ifthe one or more user intents include a user intent of resuming movieplayback and the predetermined period of time is 10 minutes, deviceselection module 1110 will determine whether a movie was paused withinthe last 10 minutes at one or more of the electronic devicesparticipating in context-sharing group 914 (based on data indicating atype of device state change and a time of device state change includedin the device state change information) because the event of pausing amovie corresponds to the user intent of resuming movie playback. In someexamples, device selection module 1110 makes this determination inresponse to determining that an event that corresponds to a user intentof the one or more user intents is not currently occurring at one ormore electronic devices participating in the context sharing group. Insome examples, device selection module 1110 determines whether an eventthat corresponds to a user intent of the one or more user intentspreviously occurred at one or more electronic devices in response todetermining that the one or more user intents include a user intent ofresuming media playback (e.g., resuming music playback, movie playback,or the like). In some of these examples, in response to determining thatthe one or more user intents include a user intent of resuming mediaplayback, device selection module 1110 determines whether an event thatcorresponds to a user intent of the one or more user intents previouslyoccurred at one or more electronic devices within a predetermined periodof time instead of determining whether an event that corresponds to auser intent of the one or more user intents is currently occurring atone or more electronic device.

In the above examples, if device selection module 1110 determines thatan event that corresponds to a user intent of the one or more userintents previously occurred at a single electronic device participatingin the context-sharing group within the predetermined period of time,device selection module 1110 selects the single electronic device (atwhich the event previously occurred) to perform the one or more tasks.For example, if a user intent is resuming music playback and deviceselection module 1110 determines that communal device 904 was the onlyelectronic device participating in context-sharing group 914 to pausemusic playback within the predetermined period of time (e.g., 30minutes), then device selection module 1110 selects communal device 904.

Alternatively, if device selection module 1110 determines that an eventthat corresponds to a user intent of the one or more user intentspreviously occurred at two or more electronic devices participating inthe context-sharing group within the predetermined period of time,device selection module 1110 determines, based on proximity informationincluded in the aggregate context (e.g., proximity informationassociated with one or more electronic devices participating in thecontext sharing group), which electronic device of the two or moreelectronic devices is physically closest to the electronic device thatprovided the user voice input data to voice input receiver module 1102(e.g., because that electronic device is likely the closest device tothe user that provided the user voice input). Returning to the previousexample, if device selection module 1110 determines that user device 906also paused music playback within the predetermined period of time (inaddition to communal device 904), device selection module 1110 willdetermine whether user device 906 or communal device 904 is closer tocommunal device 904 (i.e., the device that provided the datacorresponding to user voice input 918 to voice input receiver module1102). In this case, communal device 904 is the closest device becausecommunal device 904 itself provided the data corresponding to user voiceinput 918 to voice input receiver module 1102. Thus, in this example,device selection module 1110 would select communal device 904 to performthe one or more tasks. Determining which electronic device is closest inthese examples prevents an electronic device that is located in anentirely different area of the location associated with thecontext-sharing group (e.g., from where the user is located) from beingselected (e.g., and subsequently resuming media playback).

In some examples, the proximity information is based on data included inone or more trigger indications (e.g., associated with one or moreelectronic devices participating in the context-sharing group) that areincluded in the aggregate context. Specifically, as discussed above,each trigger indication includes data indicating whether or not anelectronic device detected a digital assistant trigger included in theuser voice input, such as data indicating an energy level (e.g., decibellevel) of the detected digital assistant trigger (e.g., the energy levelof the digital assistant trigger when received by an electronic device).In these examples, determining which electronic device of the two ormore electronic devices is physically closest to the electronic devicethat provided the user voice input data to voice input receiver module1102 includes device selection module 1110 comparing the digitalassistant trigger energy levels of the two or more electronic devicesand determining which electronic device corresponds to the highestenergy level. Device selection module then selects the electronic devicewith the highest digital assistant trigger energy level to perform theone or more tasks.

In some examples, device selection module 1110 determines whichelectronic device of the two or more electronic devices is physicallyclosest to the electronic device that provides the user voice input datato voice input receiver module 1102 based on contextual stateinformation included in the aggregate context (e.g., instead of, or inaddition to, proximity information). Specifically, in examples where thecontextual state information includes a current location of electronicdevices participating in the context-sharing group (e.g., based on GPSdata from GPS module 235 and/or information from a software applicationthat has context-sharing group functionality (e.g., HomeKit®)), deviceselection module 1110 compares the current location of the two or moreelectronic devices and determines which electronic device is physicallyclosest to the electronic device that provided the voice input data tovoice input receiver module 1102 based on the comparison. Deviceselection module 1110 then selects the closest electronic device toperform the one or more tasks.

In some examples, if device selection module 1110 determines, based onproximity information and/or contextual state information included inthe aggregate context, that two or more electronic devices are equallyas physically close to the electronic device that provided the uservoice input data voice input receiver module 1102, device selectionmodule 1110 selects the two or more electronic devices (instead ofselecting a single electronic device). In some examples, two or moreelectronic devices are equally as physically close to the electronicdevice that provided the user voice input data to voice input receivermodule 1102 if a difference between their respective digital assistanttrigger energy levels is less than a predetermined threshold (e.g., lessthan 5 decibels). For example, if the digital assistant trigger energylevels of communal device 904 and user device 906 are 40 decibels and 42decibels, respectively, and the predetermined threshold is 5 decibels,device selection module 1110 will determine that communal device 904 anduser device 906 are equally as physically close to communal device 904(i.e., the device that provided the data corresponding to user voiceinput 918). In some examples, two or more electronic devices are equallyas physically close to the electronic device that provided the uservoice input data to voice input receiver module 1102 if contextual stateinformation associated with each of two or more electronic devicesindicates that the two or more electronic devices are each currentlylocated within a same area of the location associated with the contextsharing group (e.g., the same room, same office, or the like)).

In some examples, in response to determining that an event thatcorresponds to a user intent of the one or more user intents previouslyoccurred at two or more electronic devices within the predeterminedperiod of time, device selection module 1110 simply selects the two ormore electronic devices instead of determining which electronic deviceof the two or more electronic devices is physically closest to theelectronic device that provided the user voice input data to voice inputreceiver module 1102.

As will be described in greater detail below, when device selectionmodule 1110 selects two or more electronic devices in the aboveexamples, device selection module 1110 provides command module 1112 with(1) device identifiers corresponding to the two or more electronicdevices, (2) the one or more tasks, and (3) an instruction to provide acommand that causes the electronic device that provided the user voiceinput data to voice input receiver module 1102 (e.g., communal device904) to output a query requesting the user to select an electronicdevice of the two or more electronic devices to perform the one or moretasks.

If device selection module 1110 determines that an event thatcorresponds to a user intent of the one or more user intents is notcurrently occurring at an electronic device participating in thecontext-sharing group (and, in some examples, that an event thatcorresponds to a user intent did not previously occur at an electronicdevice within a predetermined period of time), device selection module1110 determines that the user intent corresponds to a user request forcausing a new event to occur at one or more electronic devicesparticipating in the context-sharing group. For example, if the userintent is playing music (e.g., based on the user voice input “Hey Siri,play a Taylor Swift song.”) and device selection module 1110 determines(based on device state change information included in the aggregatecontext) that a music playback event is not occurring at any of theelectronic devices participating in context-sharing group 914, deviceselection module 1110 will determine that the user intent corresponds toa user request for causing a new event (in this case, music playback) tooccur at one or more electronic devices of context-sharing group 914.

After determining that the user intent corresponds to a user request forcausing a new event to occur, device selection module 1110 determines,based on device state change information included in the aggregatecontext (e.g., time of device state change, type of device state change,etc.), whether one or more electronic devices participating in thecontext-sharing group are available to perform the one or more tasks. Insome examples, device selection module 1110 determines whether one ormore electronic device is available further based on contextual stateinformation associated with the electronic device (e.g., data indicatinga display visibility of the electronic device). An electronic device isnot available to perform the one or more tasks if the device statechange information and/or contextual state information associated withthe electronic device indicates that the electronic device is currentlybeing used by a user (e.g., open/active software applications),currently performing a task, and/or currently unable to provide an audioand/or visual output (e.g., because the electronic device is face down,muted, playing media, and/or the like). For example, if the device statechange information associated with communal device 908 indicates thatcommunal device 908 is currently playing a movie, device selectionmodule 1110 will determine that communal device 908 is not available toperform the one or more tasks. As another example, if the device statechange information associated with user device 906 indicates that agaming software application stored on user device 906 is currently open(e.g., such that a user is interacting with the gaming softwareapplication), device selection module 1110 will determine that userdevice 906 is not available to perform the one or more tasks.

If device selection module 1110 determines that one or more electronicdevices are available to perform the one or more tasks, device selectionmodule 1110 determines, based on device capability information includedin the aggregate context (e.g., type of device, processing power, memoryavailability, display information (e.g., a size of display), speakerinformation (e.g., a loudness of the speaker), and/or the like), whethereach of the one or more available electronic devices is capable ofperforming the one or more tasks. For example, if the one or more tasksinclude a task of displaying information, images, videos, and/or thelike, an electronic device is capable of performing the one or moretasks only if the device has a display (or is communicatively connectedto a display). As another example, if performing the one or more tasksrequires an electronic device to have a minimum amount of processingpower and/or memory, an electronic device will not be capable ofperforming the one or more tasks if the device capability informationassociated with the electronic device indicates that the electronicdevice does not have the minimum amount of processing power and/ormemory. In some examples, device selection model determines whether theone or more available electronic devices are capable of performing theone or more tasks further based on contextual state informationassociated with the one or more available electronic devices (e.g.,strength of network connection, amount of battery power, and/or thelike). In some examples, device selection module 1110 determines that anelectronic device is a capable electronic device if the electronicdevice is capable of performing at least one task of the one or moretasks.

If device selection module 1110 determines that only a single electronicdevice participating in the context-sharing group is both available andcapable of performing the one or more tasks, device selection moduleselects the single electronic device to perform the one or more tasks.

If device selection module 1110 determines that two or more electronicdevices participating in the context-sharing group are both availableand capable of performing the one or more tasks, device selection module1110 determines, based on proximity information associated with the twoor more available and capable electronic devices, which of the two ormore electronic devices is physically closest to the electronic devicethat provided the user voice input data to voice input receiver module1102. For example, if device selection module 1110 determines that userdevice 906 and communal device 908 are both available and capable ofperforming the one or more tasks, device selection module 1110 willdetermine whether user device 906 or communal device 908 is physicallycloser to communal device 904. Determining which electronic device isphysically closest to communal device 904 ensures that, for example,device selection module 1110 does not select user device 906 to performthe one or more tasks if user device 906 is in a different area of thelocation associated with the context-sharing group 914 (e.g., in adifferent room, on a different floor, and/or the like) relative tocommunal device 904 (and thus relative to user 902 (e.g., because a useris typically located near the electronic device that provides the uservoice input data to voice input receiver module 1102)). This in turnimproves a user's experience.

As discussed above, in some examples, the proximity information is basedon data included in one or more trigger indications that are included inthe aggregate context. Specifically, each trigger indication includesdata indicating whether or not an electronic device detected a digitalassistant trigger included in the user voice input, such as dataindicating an energy level (e.g., decibel level) of the detected digitalassistant trigger (e.g., the energy level of the digital assistanttrigger when received by an electronic device). In these examples,determining which electronic device of the two or more available andcapable electronic devices is physically closest to the electronicdevice that provided the user voice input data to voice input receivermodule 1102 includes device selection module 1110 comparing the digitalassistant trigger energy levels of the two or more available and capableelectronic devices and determining which electronic device correspondsto the highest energy level. Device selection module then selects theelectronic device with the highest digital assistant trigger energylevel to perform the one or more tasks.

In some examples, device selection module 1110 determines whichelectronic device of the two or more available and capable electronicdevices is physically closest to the electronic device that provides theuser voice input data to voice input receiver module 1102 based oncontextual state information included in the aggregate context (e.g.,instead of, or in addition to, proximity information). Specifically, inexamples where the contextual state information includes a currentlocation of electronic devices participating in the context-sharinggroup (e.g., based on GPS data from GPS module 235 and/or informationfrom a software application that has context-sharing group functionality(e.g., HomeKit®)), device selection module 1110 compares the currentlocation of the two or more available and capable electronic devices anddetermines which electronic device is physically closest to theelectronic device that provided the voice input data to voice inputreceiver module 1102 based on the comparison. Device selection module1110 then selects the closest electronic device to perform the one ormore tasks.

In some examples, if device selection module 1110 determines, based onproximity information and/or contextual state information included inthe aggregate context, that two or more available and capable electronicdevices are equally as physically close to the electronic device thatprovided the user voice input data voice input receiver module 1102,device selection module 1110 determines, based on user attentioninformation included in the aggregate context (e.g., data indicatingwhether a user is currently looking at a display of an electronic device(e.g., based on information from an optical sensor 264 on the frontand/or back of the electronic device)), whether a user of the electronicdevice that provided the voice input data to voice input receiver module1102 (e.g., the user that provided the user voice input) is looking at adisplay of an electronic device of the two or more available and capableelectronic devices. As described above, in some examples, two or moreelectronic devices are equally as physically close to the electronicdevice that provided the user voice input data to voice input receivermodule 1102 if a difference between their respective digital assistanttrigger energy levels is less than a predetermined threshold (e.g., lessthan 5 decibels). In some examples, two or more electronic devices areequally as physically close to the electronic device that provided theuser voice input data to voice input receiver module 1102 if contextualstate information associated with each of two or more electronic devicesindicates that the two or more electronic devices are each currentlylocated within a same area of the location associated with the contextsharing group (e.g., the same room, same office, or the like)).

In some examples, if device selection module 1110 determines, based onthe user attention information associated with the two or more availableand capable electronic devices, that a user of the electronic devicethat provided the user voice input data to voice input receiver module1102 is looking at a single electronic device of the two or moreavailable and capable electronic devices, device selection module 1110selects the single electronic device to perform the two or more tasks.For example, if user device 906 and user device 910 are both (1)available and capable of performing the one or more tasks and (2)equally as physically close to communal device 904 (e.g., both devicesare in the same room), but user attention information associated withthe devices indicates that user 902 is looking at user device 906 (andnot at user device 910), device selection module 1110 will select userdevice 906 to perform the one or more tasks. Selecting and electronicdevice that a user is looking at when two or more available and capableelectronic devices are equally as physically close (as described above)improves a user's experience. For example, if the one or more tasksinclude the display of information, images, videos, or the like, a userwill already be looking at the correct display to view the displayedinformation, images, videos, or the like instead of having to turn hisor her attention to a display of another electronic device. This in turnimproves a user's experience.

In some of the above examples, if the two or more available, capable,and physically close electronic devices includes the electronic devicethat provided the user voice input data to voice input receiver module1102, but device selection module 1110 determines that a user is onlylooking at another electronic device of the two or more available andcapable electronic devices, device selection module 1110 selects theelectronic device that provided the user voice input data to voice inputreceiver module 1102. As will be described in greater detail below, insome examples, after making the above selection, device selection module1110 instructs command module 1112 to provide a command that causes theselected electronic device to perform the one or more tasks and/oroutput (e.g., as an audio output and/or on a display) an offer tohandoff the performance of the one or more tasks to the electronicdevice that the user is looking at. Device selection module provides theabove instruction in addition to providing command module 1112 with thedevice identifier corresponding to the selected electronic device andthe one or more tasks.

In some examples, if device selection module 1110 determines, based onthe user attention information associated with the two or more availableand capable electronic devices, that a user of the electronic devicethat provided the user voice input data to voice input receiver module1102 is not looking at any of the two or more available and capableelectronic devices (e.g., because none of the two or more available andcapable electronic devices has a display or a communicatively connecteddisplay), device selection module 1110 determines, based on dataindicating a display size included in device capability informationassociated with the two or more available and capable electronicdevices, which electronic device of the two or more available andcapable electronic devices has the largest display (includingcommunicatively-connected displays (e.g., displayscommunicatively-connected to a smart TV)). For example, if deviceselection module 1110 determines that (1) user device 906 and communaldevice 908 are both available and capable of performing the one or moretasks, (2) user device 906 and communal device 908 are both equally asphysically close to communal device 904 (e.g., both devices are in thesame room), and (3) user 902 is not looking at user device 906 orcommunal device 908, then device selection module 1110 will determinewhether user device 906 or communal device 908 has (or iscommunicatively connected to) the largest display. Device selectionmodule 1110 then selects the single electronic device of the two or moreavailable and capable electronic devices that has (or is communicativelyconnected to) the largest display.

In some examples, if device selection module 1110 determines, based onthe user attention information associated with the two or more availableand capable electronic devices, that a user of the electronic devicethat provided the user voice input data to voice input receiver module1102 is not looking at any of the two or more available and capableelectronic devices, device selection module 1110 determines, based ondata indicating a speaker loudness (e.g., maximum decibel level)included in device capability information associated with the two ormore available and capable electronic devices, which electronic deviceof the two or more available and capable electronic devices has (or iscommunicatively connected to) the loudest speaker(s). For example, ifdevice selection module 1110 determines that (1) user device 906 andcommunal device 908 are both available and capable of performing the oneor more tasks, (2) user device 906 and communal device 908 are bothequally as physically close to communal device 904 (e.g., both devicesare in the same room), and (3) user 902 is not looking at user device906 or communal device 908, then device selection module 1110 willdetermine whether user device 906 or communal device 908 has (or iscommunicatively connected to) the largest speaker(s). Device selectionmodule 1110 then selects the single electronic device of the two or moreavailable and capable electronic devices that has (or is communicativelyconnected to) the loudest speaker(s).

In some examples, if device selection module 1110 determines, based onthe user attention information associated with the two or more availableand capable electronic devices, that a user of the electronic devicethat provided the user voice input data to voice input receiver module1102 is not looking at any of the two or more available and capableelectronic devices, device selection module 1110 simply selects the twoor more available and capable electronic devices. As will be describedin greater detail below, when device selection module 1110 selects twoor more available and capable electronic devices in the above examples,device selection module 1110 provides command module 1112 with (1)device identifiers corresponding to the two or more available andcapable electronic devices, (2) the one or more tasks, and (3) aninstruction to provide a command that causes the electronic device thatprovided the user voice input data to voice input receiver module 1102(e.g., communal device 904) to output a query requesting the user toselect an electronic device of the two or more electronic devices toperform the one or more tasks.

As will be described in greater detail below with reference to FIGS.12A-12B, in some examples, if task determination module 1108 determinesa plurality of tasks (e.g., more than one task) and device selectionmodule 1110 determines, based on proximity information and/or contextualstate information included in the aggregate context, that two or moreavailable and capable electronic devices are equally as physically closeto the electronic device that provided the user voice input data voiceinput receiver module 1102, device selection module 1110 selects atleast two of the two or more electronic devices to each perform at leastone task of the plurality of tasks. These examples are referred to as“multimodal task performance,” as the above selection results in two ormore electronic devices concurrently performing tasks (of the pluralityof tasks) to fulfill a user request. For example, if device selectionmodule 1110 determines that user device 906 and communal device 908 areboth available, capable, and proximate to communal device 904 (e.g., inthe same room), device selection module may select both user device 906and communal device 908 to perform at least one task of the plurality oftasks. In these examples, after selecting at least two electronicdevices to perform the one or more tasks, device selection module 1110assigns a set of tasks of the plurality of tasks to each of the selectedelectronic devices. A set of tasks can include one task of the pluralityof tasks or multiple tasks of the plurality of tasks. Returning to theabove example, device selection module 1110 may assign a first set oftasks to user device 906 (e.g., performing a search, retrievingdata/information, and providing an audio output including the retrieveddata/information (e.g., a digital assistant response)) and a second setof tasks to communal device 908 (e.g., performing a search, retrievingdata/information, and providing (e.g., displaying) a visual outputincluding the retrieved data/information (e.g., a textual representationof the digital assistant response output by user device 906)). As notedin the example above, in some examples, device selection module assignsone or more of the same tasks to each of the at least two selectedelectronic devices. For example, device selection module 1110 may assignthe tasks of performing a search and retrieving data/information basedon the search to all of the selected electronic devices (e.g., such thateach electronic device is able to provide an output including theretrieved data/information).

In some examples, device selection module 1110 selects at least two ofthe two or more available, capable, and proximate electronic devices formultimodal task performance instead of determining, based on userattention information included in the aggregate context, whether a useris looking at an electronic device of the two or more electronicdevices. In some examples, device selection module 1110 selects at leasttwo of the two or more available, capable, and proximate electronicdevices for multimodal task performance even if device selection module1110 determines that a user of the electronic device that provided theuser voice input data to voice input receiver module 1102 is looking ata single electronic device of the two or more available, capable, andproximate electronic devices.

In some examples, device selection module 1110 selects the at least twoelectronic devices for multimodal task performance based on theplurality of tasks including one or more specific tasks (e.g., if theplurality of tasks include displaying a particular type of information(e.g., images, recipes, or the like), if the plurality of tasks includeproviding an audio output and a visual output, if the plurality of tasksinclude user authentication (e.g., to make a purchase), or the like). Inthese examples, if device selection module 1110 determines that theplurality of tasks includes one or more specific tasks, device selectionmodule 1110 selects the at least two electronic devices for multimodaltask performance instead of (1) determining whether a user is looking atan electronic device and/or (2) selecting a single electronic devicethat the user is looking at. For example, device selection module 1110may select the at least two electronic devices for multimodal taskperformance if device selection module 1110 determines that theplurality of tasks includes a task of user authentication.

In some examples, device selection module selects the at least twoelectronic devices for multimodal task performance based on thedetermined user intent corresponding to the plurality of tasks. In theseexamples, device selection module selects the at least two electronicdevices for multimodal task performance instead of (1) determiningwhether a user is looking at an electronic device and/or (2) selecting asingle electronic device that the user is looking at. For example, ifthe plurality of tasks correspond to a user intent of providing a foodrecipe or a user intent of purchasing a movie, device selection module1110 will select at least two electronic devices for multimodal taskperformance in response to determining that the at least two electronicdevices are available, capable, and proximate to the electronic devicethat provided the user voice input data to voice input receiver module1102.

As will be described in greater detail below, when device selectionmodule 1110 selects at least two electronic devices for multimodal taskperformance in the above examples, device selection module 1110 providescommand module 1112 with (1) device identifiers corresponding to the atleast two electronic devices, (2) a set of tasks (of the plurality oftasks) associated with each device identifier, and (3) an instruction toprovide a command to each of the selected electronic devices that causeseach electronic device to perform its associated set of tasks.

In some examples, device selection module 1110 determines that none ofthe electronic devices participating in the context-sharing group areavailable. For example, all of the electronic devices in context-sharinggroup would be unavailable if context information included in theaggregate context indicates that user device 906 and user device 910 areface down (and thus do not have visible displays) and if communal device904 and communal device 908 are already performing a task for a userand/or have an open/active software application (e.g., that a user isinteracting with). In these examples, device selection module 1110selects a single capable and/or proximate electronic device (proximateto the electronic device that provided the voice input data to voiceinput receiver module 1102) as described above. In some examples, deviceselection module selects more than one capable and/or proximateelectronic device. Then, as will be described in greater detail below,device selection module 1110 provides command module 1112 with (1) adevice identifier corresponding to the selected electronic device, (2)the one or more tasks, and (3) an instruction to provide a command thatcauses the selected electronic device to output results of theperformance of the one or more tasks (e.g., data retrieved based on theperformance of the one or more tasks, audio and/or text output datagenerated based on the performance of the one or more tasks, etc.)within a notification. In some examples, the notification includesretrieved data/information. In some examples, the notification providesa link or an affordance that, when selected (e.g., pressed) by a user ofthe electronic device, causes the electronic device to output a digitalassistant response as an audio output and/or as text on a display of theelectronic device (e.g., a digital assistant response that includesretrieved data/information).

As described above, in some examples, system 1100 is able to access andutilize user data associated with one or more electronic devicesparticipating in a context-sharing group when that user data is, forexample, stored on the one or more remote devices that are implementingsystem 1100 (e.g., server 916). For example, user intent module 1106 mayaccess and utilize user data when determining the one or more userintents. Similarly, in some of the above examples, after deviceselection module 1110 selects an electronic device to perform the one ormore tasks (e.g., before device selection module provides deviceidentifiers, the one or more tasks, and/or instructions to commandmodule 1112), device selection module 1110 determines, based on thedetermined user intent and/or the one or more tasks, whether or notthere is user data (e.g., a user's media, contacts, speech profiles,preferences, or the like) that is stored on the one or more remotedevices that is needed for the performance of the one or more tasks. Forexample, if the one or more tasks include a task of playing a specificsong (e.g., a song by a specific artist (e.g., based on the user voiceinput “Hey Siri, play a Taylor Swift song.”)), device selection modulemay determine that audio data corresponding to the specific song isneeded to perform the one or more tasks.

If device selection module 1110 determines that there is stored userdata needed for the performance of the one or more tasks, deviceselection module determines whether the selected electronic device hasaccess to that stored user data (e.g., if the stored user data is alsostored locally on the selected electronic device, such that the selectedelectronic device may access and utilize the user data when performingthe one or more tasks). Device selection module 1110 makes thisdetermination based on the user data associated with the selectedelectronic device that is stored on the one or more remote devices(e.g., because the user data stored on the one or more remote devicesindicates what user data is stored on the selected electronic devicewhen, for example, the selected electronic device periodicallysyncs/transmits its stored user data to the one or more remote devices).Specifically, if the user data that is needed to perform the one or moretasks is not included in the user data associated with the selectedelectronic device that is stored on the one or more remote devices(e.g., the user data is only included in the stored user data associatedwith another electronic device participating in the context-sharinggroup), then device selection module 1110 determines that the selectedelectronic device does not have access to the user data that is needed.Returning to the previous example, if the selected electronic device isuser device 906 and device selection module determines that the userdata associated with user device 906 (stored on server 916) does notinclude the audio data corresponding to the specific song (e.g., theaudio data is only included in stored user data associated with one ormore other electronic devices (e.g., user device 910)), device selectionmodule 1110 will determine that user device 906 does not have access tothe audio data.

If device selection module 1110 determines that the selected electronicdevice does not have access to the user data needed to perform the oneor more tasks, device selection module retrieves the stored user dataand provides the user data to command module 1112 (e.g., when deviceselection module 1110 provides the device identifiers, one or moretasks, and/or instructions to command module 1112). Specifically, deviceselection module provides command module 1112 with (1) a deviceidentifier corresponding to the selected electronic device, (2) the oneor more tasks associated with the device identifier, (3) the retrieveduser data, and (4) an instruction to provide a command to the selectedelectronic device that causes the selected electronic device to performthe one or more tasks based on the retrieved user data. Returning to theprevious example, after determining that user device 906 does not haveaccess to the stored audio data corresponding to the specific song,device selection module 1110 will retrieve the audio from the storeduser data associated with another electronic device participating incontext-sharing group 914 (e.g., user device 910) and subsequentlyprovide the audio data to command module 1112 with the device identifiercorresponding to user device 906 so that command module 1112 maygenerate a command that will cause user device 906 to play the specificsong using the retrieved audio data.

In some examples, the other electronic device that is associated withthe retrieved user data (e.g., user device 910) must be registered tothe user that provides the user voice input (e.g., user 902) in orderfor device selection module 1110 to retrieve the user data for taskperformance at the selected electronic device (e.g., user device 906).For example, if user device 906 and user device 910 are registered totwo separate users, device selection module 1110 will not be able toretrieve stored user data associated with user device 910 for taskperformance at user device 906 (and vice versa). In other examples,device selection module 1110 can retrieve stored user data associatedwith any electronic device that is currently participating in thecontext-sharing group (even if the registered user for an electronicdevice is different from the registered user that provided the uservoice input).

In some examples, device selection module 1110 retrieves stored userdata associated with an electronic device registered to the user thatprovides the user voice input only if the electronic device isparticipating in the same context-sharing group as the selectedelectronic device. For example, if user 902 is the registered user ofanother electronic device that is not currently participating incontext-sharing group 914, then device selection module 1110 cannotretrieve user data associated with that other electronic device untilthat other electronic device joins context-sharing group 914. As anotherexample, if user device 910 is registered to user 902, but user device910 leaves context-sharing group 914 (e.g., by disconnecting fromnetwork 912) before device selection module 1110 retrieves user datafrom the stored user data associated with user device 910, then deviceselection module 1110 will not be able to retrieve user data from thestored user data associated with user device 910 or provide that userdata to command module 1112. Note, in some examples, communal devices(e.g., communal device 904) do not store user data and/or do not syncuser data to remote devices (e.g., server 916). In these examples,device selection module 1110 can only retrieve and provide user dataassociated with user devices (e.g., user device 906 and/or user device910) that are registered to the user that provides the user voice input.

System 1100 includes command module 1112. Command module 1112 (1)receives device identifiers, tasks, instructions, and/or user data fromdevice selection module 1110, (2) generates one or more commands basedon the received device identifiers, tasks, instructions, and/or userdata, and (3) provides the one or more commands with associated deviceidentifiers (and, in some examples, user data) to the electronic devicethat provided the voice input data to voice input receiver module 1102(e.g., because that is the only electronic device participating in thecontext-sharing group that the remote device (e.g., server 916) is incommunication with). For example, after determining one or morecommands, command module 1112 will transmit the one or more commands anda device identifier associated with each command to communal device 904.As discussed above, the commands generated by command module 1112 willcause electronic devices to perform various tasks based on thedeterminations and selections made by device selection module 1110.Specifically, there are several ways in which the one or more commandsgenerated by command module 1112 may vary based on the deviceidentifiers, tasks, instructions, and/or user data received from deviceselection module 1110, each of which is discussed in turn below.

If command module 1112 receives (1) a single device identifiercorresponding to a selected electronic device and (2) one or more tasks,command module 1112 will generate a command that will cause the selectedelectronic device to perform the one or more tasks. In some examples,the command further causes the selected electronic device to output anaudio and/or visual digital assistant response based on the performanceof the one or more tasks (e.g., “I have stopped your alarm.” or “Nowplaying Taylor Swift.”). In some examples, command module 1112 generatesan additional command that will cause the electronic device thatprovided the user voice input data to voice input receiver module 1102(e.g., communal device 904) to output an audio and/or visual digitalassistant response that indicates which electronic device was selectedto perform the one or more tasks (e.g., “Directions to San Jose Airportare ready on your phone.” or “Now showing photos on your TV.”).

If command module 1112 receives (1) two or more device identifierscorresponding to two or more electronic devices, (2) the one or moretasks, and (3) an instruction to provide a command that causes theelectronic device that provided the user voice input data to voice inputreceiver module 1102 (e.g., communal device 904) to output a queryrequesting the user to select an electronic device of the two or moreelectronic devices to perform the one or more tasks, command module 1112will generate two commands. The first command will cause theuser-selected electronic device to perform the one or more tasks. Thesecond command will cause the electronic device that provided the uservoice input data to voice input receiver module 1102 to (1) output aquery (e.g., as an audio output and/or as text on a display) requestingthe user to select an electronic device of the two or more selectedelectronic devices to perform the one or more tasks (e.g., “Do you wantto see your photos on your iPhone or your iPad?”) and (2) transmit thefirst command to the user-selected electronic device (e.g., afterreceiving the user's response to the query (e.g., the user's responsebeing a second user voice input or a selection of a displayed affordancecorresponding to one of the two or more electronic devices)).

In some examples, the first command further causes the user-selectedelectronic device to output an audio and/or visual digital assistantresponse based on the performance of the one or more tasks (e.g., “Ihave stopped your alarm.” or “Now playing Taylor Swift.”). In someexamples, the second command further causes the electronic device thatprovided the user voice input data to voice input receiver module 1102to output an audio and/or visual digital assistant response afterreceiving the user selection that indicates the electronic device thatwas selected to perform the one or more tasks (e.g., “Now showing photoson your iPad.”).

If command module 1112 receives (1) a device identifier corresponding tothe selected electronic device, (2) the one or more tasks, and (3) aninstruction to provide a command that causes the selected electronicdevice to output results of the performance of the one or more taskswithin a notification, command module 1112 will generate a command thatwill cause the selected electronic device to perform the one or moretasks and subsequently provide a notification (e.g., a notification thatappears on a lock-screen interface of the selected electronic device, ina notification history interface of the selected electronic device,and/or the like) that includes results of the performance of the one ormore tasks. In some examples, the command further causes the selectedelectronic device to output an audio indication when the notification isprovided. In some examples, command module 1112 generates an additionalcommand that will cause the electronic device that provided the uservoice input data to voice input receiver module 1102 (e.g., communaldevice 904) to output an audio and/or visual digital assistant responsethat indicates that none of the electronic devices participating in thecontext-sharing group are available to perform the one or more tasksand/or indicates that further information related to the user's requestmay be found on the selected electronic device (e.g., “None of yourdevices can show pictures at the moment. Please see your iPhone for moreinformation.”).

If command module 1112 receives (1) a device identifier corresponding tothe selected electronic device, (2) the one or more tasks, (3) aninstruction to provide a command that causes the selected electronicdevice to output (e.g., as an audio output and/or on a display) an offerto handoff the performance of the one or more tasks to anotherelectronic device (e.g., an electronic device that the user is lookingat), and (4) a second device identifier corresponding to the otherelectronic device, command module 1112 will generate a command that willcause the selected electronic device to output the offer to handoff theperformance of the one or more tasks to the other electronic devicecorresponding to the second device identifier (e.g., “Would you preferto see the lasagna recipe on your iPad?”). In some examples, the commandfurther causes the selected electronic device to perform the one or moretasks and subsequently output the offer to handoff the performance ofthe one or more tasks to the other electronic device along with resultsof the performance of the one or more tasks (e.g., “Here is a lasagnarecipe that I found. Did you want to see that on your iPad?”).

If command module receives (1) device identifiers corresponding to twoor more selected electronic devices, (2) a set of tasks associated witheach device identifier, and (3) an instruction to provide a command toeach of the two or more selected electronic devices that causes eachelectronic device to perform its associated set of tasks, command module1112 will generate a command for each device identifier. For example, ifcommand module 1112 receives a device identifier corresponding to userdevice 906, a device identifier corresponding to communal device 908,and a sets of tasks associated with each device identifier, commandmodule 1112 will generate a first command that will cause user device906 to perform its associated set of tasks and a second command thatwill cause communal device 908 to perform its associated set of tasks.In some examples, at least one command of the two or more commands thatcommand module 1112 generates further causes a selected electronicdevice to output an audio and/or visual digital assistant response basedon the performance of the one or more tasks (e.g., “There are severalStar Wars movies to choose from, as shown on your TV. The first movie is. . . ”).

In some examples, command module 1112 determines whether or not a set oftasks received from device selection module 1110 includes a task of userauthentication (e.g., user authentication to make a purchase). In theseexamples, if command module 1112 determines that a set of tasks includesa task of user authentication, command module 1112 will transmit thatset of tasks to the electronic device that provided the user voice inputdata to voice input receiver module 1102 (e.g., communal device 904) andforgo transmitting the commands corresponding to the remaining sets oftasks. Command module 1112 will forgo transmitting the commandscorresponding to the remaining sets of tasks until command module 1112(or one or more other modules of system 1100) authenticates a user(e.g., based on a comparison of stored user authentication data toauthentication data provided to the electronic device that performs theset of tasks that includes a task of user authentication) or untilcommand module 1112 (or one or more other modules of system 1100)receives an indication that a user has been authenticated from theelectronic device that provided the user voice input data (e.g., whenthe electronic device that performs the set of tasks locallyauthenticates a user instead of providing the authentication data forcommand module 1112 to authenticate the user). After authenticating auser or receiving an indication that a user has been authenticated,command module transmits the commands corresponding to the remainingsets of tasks to the electronic device that provided the user voiceinput data. An example of this process is described in greater detailbelow with reference to FIG. 12B.

If command module 1112 receives (1) a device identifier corresponding toa selected electronic device, (2) one or more tasks associated with thedevice identifier, (3) retrieved user data, and (4) an instruction toprovide a command to the selected electronic device that causes theselected electronic device to perform the one or more tasks based on theretrieved user data, command module 1112 will generate a command thatwill cause the selected electronic device to perform the one or moretasks based on the retrieved user data. In some examples, the commandfurther causes the selected electronic device to output an audio and/orvisual digital assistant response based on the performance of the one ormore tasks (e.g., “Now playing Taylor Swift.” or “Calling DaenerysTargaryen.”). In some examples, command module 1112 generates anadditional command that will cause the electronic device that providedthe user voice input data to voice input receiver module 1102 (e.g.,communal device 904) to output an audio and/or visual digital assistantresponse that indicates which electronic device was selected to performthe one or more tasks (e.g., “Now playing Taylor Swift on your HomePod.”or “Calling Daenerys Targaryen on your iPhone.”).

Note, while the above description separately describes the differenttypes of commands that command module 1112 generates, it should beappreciated that, in some examples, command module 1112 generates morethan one type of command in response to a single user voice input. Forexample, if user voice input 918 is “Hey Siri, play a Taylor Swiftsong,” device selection module 1110 may provide command module 1112 with(1) an instruction to provide a command that causes communal device 904to output a query requesting user 902 to select an electronic device toperform the one or more tasks, (2) retrieved audio data corresponding toa Taylor Swift song, and (3) an instruction to provide a command to theuser-selected electronic device that causes the user-selected electronicdevice to perform the one or more tasks based on the retrieved audiodata. In response, command module 1112 may generate a first command thatwill cause the user-selected electronic device to perform the one ormore tasks based on the retrieved audio data and a second command thatwill cause communal device 904 to (1) output a query (e.g., as an audiooutput and/or as text on a display) requesting the user to select anelectronic device of two or more selected electronic devices to performthe one or more tasks based on the retrieved audio data and (2) transmitthe first command to the user-selected electronic device along with theretrieved audio data. Thus, as shown in the above example, commandmodule 1112 generates a first type of command (e.g., directed to theperformance of one or more tasks based on retrieved user data) and asecond type of command (e.g., directed to the user selection of anelectronic device that will perform the one or more tasks) in responseto a single user voice input.

After generating one or more commands (e.g., as described above),command module 1112 transmits the one or more commands (with associateddevice identifiers) to the electronic device that provided the uservoice input data to voice input receiver module 1102. In the examplesdescribed above where command module 1112 receives user data retrievedby device selection module 1110, command module 1112 further transmitsthe user data (with associated device identifiers) to the electronicdevice that provided the user voice input data to voice input receivermodule 1102. As will be described in greater detail below with referenceto FIG. 9, after receiving the one or more commands (and, in someexamples, user data), the electronic device that provided the user voiceinput data to voice input receiver module 1102 transmits the one or morecommands to one or more electronic device participating in thecontext-sharing group based on the device identifiers associated withthe one or more electronic devices.

Returning to FIG. 9, as represented by arrows 926, communal device 904receives, from server 916, a command to perform one or more tasks (e.g.,generated by command module 1112) and a device identifier (associatedwith the command) that corresponds to user device 906. In some examples,communal device 904 also receives user data that was stored on server916 (e.g., when the command is to perform one or more tasks based on theuser data). It should be appreciated that although arrows 926 representcommunal device receiving a single command to perform one or more tasksat a single selected electronic device, communal device 904 mayalternatively or additionally receive any of the types of commandsdescribed above with reference to command module 1112 (or anycombination of those command types).

As represented by arrows 928 and 928 a, after receiving the command toperform the one or more tasks and device identifier corresponding touser device 906, communal device 904 transmits the command to userdevice 906 (e.g., based on the stored associations between electronicdevices participating in context-sharing group 914 and their deviceidentifiers). After user device 906 receives the command, the commandcauses user device 906 to perform the one or more tasks. As discussedabove, in some examples, communal device 904 receives an additionalcommand from server 916 that causes communal device 904 to output anaudio and/or visual digital assistant response that indicates that userdevice 906 was selected to perform the one or more tasks (e.g., “I havestopped the alarm on your iPhone.” “Now showing photos on youriPhone.”).

In some examples, prior to transmitting a command to an electronicdevice (e.g., as represented by arrows 928 and 928 a), communal device904 determines whether the device identifier associated with the commandcorresponds to a client device (e.g., user device 906 or user device910). If communal device 904 determines that the device identifiercorresponds to a client device, communal device determines whether user902 is the registered user of the client device. For example, if thedevice identifier received by communal device corresponds to user device910 (instead of user device 906), communal device 904 may determinewhether user 902 is the registered user of user device 910. Then, ifcommunal device determines that user 902 is not the registered user ofuser device 910, communal device 904 determines whether user 902 is anauthorized user of user device 910.

In some examples, an authorized user is a user of a client device (otherthan the registered user of the client device) that the registered userhas granted access to control and/or make user requests on the clientdevice. In some examples, an authorized user of a client device may onlycontrol and/or make user requests on the client device when the clientdevice is participating in a context-sharing group. Authorized userinformation is provided by a registered user of a client device (e.g.,when the registered user is enrolling the client device in acontext-sharing group, or any time after) via a software applicationstored on the client device (e.g., via the HomeKit® application) and/orvia a website that has context-sharing group functionality. Thus,returning to the previous example, communal device 904 determineswhether user 902 is an authorized user of user device 910 by accessingthe authorized user information associated with user device 910 (e.g.,via the software application and/or website). In some examples,determining whether user 902 is an authorized user of user device 910includes communal device outputting a request for user authentication(e.g., voice authentication, password authentication, and/or biometricauthentication (e.g., face and/or fingerprint authentication)). Then,after receiving user authentication data from user 902, communal devicecompares the user authentication data to user authentication dataincluded in the authorized user information associated with user device910 to determine whether user 902 is an authorized user of user device910. As represented by arrows 928 and 928 b, in response to determiningthat user 902 is an authorized user of user device 910, communal device904 transmits the command to user device 910.

Note, in some examples, server 916 (e.g., device selection module 1110)determines whether user 902 is a registered user of user device 910prior to transmitting a command and a device identifier (correspondingto user device 910) to communal device 904 (e.g., as represented byarrows 926). For example, server 916 determines whether user 902 is aregistered user of user device 910 based on user data associated withuser device 910 (e.g., user voice profile information associated with aregistered user of user device 910) that is stored on server 916. Inthese examples, as represented by arrows 925, if server 916 determinesthat user 902 is not a registered user of user device 910, server 916(e.g., command module 1112) transmits a command to communal device 904that causes communal device 904 to output a request for userauthentication, receive user authentication data (from user 902), andthen determine whether user 902 is an authorized user of user device 910based on the received authentication data. Then, as represented byarrows 927, if communal device 904 determines that user 902 is anauthorized user of user device 910, communal device 904 transmits anindication that user 902 is an authorized user of user device 910 toserver 916. After receiving this indication, server 916 transmits thecommand and the device identifier (corresponding to user device 910) tocommunal device 904 (e.g., as represented by arrows 926), and communaldevice 904 transmits the command to user device 910, as represented byarrows 928 and 928 b.

6. System and Technique for Multimodal Task Performance in aContext-Sharing Group

FIGS. 12A-12B illustrate a system and technique for multimodal taskperformance in a context-sharing group, according to various examples.As shown in FIGS. 12A-12B, system 1200 includes communal device 1204,communal device 1206, and user device 1210, all of which areparticipating in context-sharing group 1214 (which is associated with aspecific location (e.g., a home, an office, or the like)). User device1210 is a client device (e.g., user device 104, 122, 200, 400, or 600).For example, user device 1210 is an iPhone®. In the examples describedbelow, user device 1210 is registered to user 1202. Communal device 1204is a smart speaker that has the same or similar digital assistantcapabilities as user device 1210. Communal device 1206 is a smart TVthat has the same or similar digital assistant capabilities as the userdevices. Communal device 1206 is communicatively connected to display1208 (e.g., a TV, a monitor, or the like). Further, communal device 1206is the context collector of context-sharing group 1214 (e.g., becausecommunal device 1206 was previously elected to be context collector). Asdiscussed above with reference to FIG. 8, communal devices are notregistered to a single user or are registered to multiple users (e.g.,such that the communal device may be used by multiple users withoutadditional user registration and/or user authentication requirements).For example, communal device 1204 is a HomePod® and communal device 1206is an Apple TV®.

System 1200 further includes network 1212 and server 1216 (e.g., DAserver 106). Network 1212 is a wireless communications network (e.g.,network(s) 110). As shown, communal device 1204, communal device 1206,and user device 1210 communicate with one another and with server 1216via network 1212 (and thus are each connected to network 1212). Server1216 is a remote device that is not participating in context-sharinggroup 1214. In some examples, system 1200 includes one or more otherremote devices (e.g., a local server, a cloud-computing system, or thelike) instead of server 1216. It should be recognized that, in theseexamples, any of the operations performed by communal device 1204,communal device 1206, and/or user device 1210 can instead be performedby server 1216. For example, server 1216 can perform the operations ofthe respective DA client modules (e.g., DA client module 229) ofcommunal device 1204, communal device 1206, and/or user device 1210.

As shown in FIG. 12A, user 1202 provides user voice input 1218 (e.g.,“Hey Siri, show me Star Wars movies.” or “Hey Siri, what is StarWars.”), which is received by communal device 1204.

As represented by arrows 1220, in response to receiving user voice input1218 (or, in some examples, in response to detecting a digital assistanttrigger included in user voice input 1218), communal device 1204transmits a request (via network 1212) to communal device 1206 (i.e.,the context collector of context-sharing group 1214) for communal device1206 to transmit an aggregate context of context-sharing group 1214 tocommunal device 1204.

As represented by arrows 1222, after receiving the request for theaggregate context from communal device 1204, communal device 1206transmits the aggregate context (or, in some examples, at least aportion of the aggregate context) to communal device 1204. In someexamples, the request for the aggregate context causes communal device1206 to transmit the aggregate context (e.g., data corresponding to theaggregate context), or at least a portion of the aggregate context, tocommunal device 1204. The aggregate context transmitted to communaldevice 1204 includes context information (e.g., device state changeinformation, contextual state information, device capabilityinformation, proximity information, and/or the like) associated with atleast communal device 1204, communal device 1206, and user device 1210(e.g., because communal device 1204, communal device 1206, and userdevice 1210 each recently underwent a device state change (e.g., a timerevent, detecting a digital assistant trigger, playing a movie, etc.)).Specifically, the context information is associated with at leastcommunal device 1204, communal device 1206, and user device 1210 basedon the device identifiers that communal device 1206 receives with thecontext information from at least communal device 1204, communal device1206, and user device 1210. In some examples, the aggregate context doesnot include any other type of device identification or identifyinginformation other than the device identifiers received with contextinformation included in the aggregate context.

In other examples, the aggregate context does include other types ofdevice identifications and/or information identifying a registered userof each electronic device (in addition to the device identifiers). Thisin turn allows server 1216 to determine whether electronic devicesparticipating in a context-sharing group are registered to a single useror two or more different users (as this information may influence thecommands that server 1216 provides). In some examples, deviceidentifications and/or information identifying a registered user of eachelectronic device included in the aggregate context allows server 1216to determine whether or not a user voice input is provided by aregistered. Further, in some examples, server 1216 uses this additionalidentifying information to access and/or utilize user data that isstored on server 1216 and that is associated with one or more of theelectronic devices (e.g., user data that an electronic deviceparticipating in the context-sharing group 914 previouslysynced/transmitted to the remote devices (e.g., during an automaticand/or periodic user data sync)).

As represented by arrows 1224, after receiving the aggregate contextfrom communal device 1206, communal device 1204 transmits datacorresponding to user voice input 1218 and at least a portion of theaggregate context to server 1216.

In some examples, communal device 1204 provides audio data correspondingto user voice input 1218 to server 1216. In some examples, communaldevice 1204 performs speech-to-text processing of user voice input 1218(e.g., using STT processing module 730) and provides text datacorresponding to user voice input 1218 (e.g., a textual representationof user voice input 1218) to server 1216. In some examples, communaldevice 1204 further performs natural language processing of the textdata corresponding to user voice input 1218 (e.g., using naturallanguage processing module 732) and provides results of the naturallanguage processing (e.g., one or more user intents) to server 1216.

In some examples, communal device 1204 provides all of the aggregatecontext to server 1216. In some examples, communal device 1204determines what context information included in the aggregate context isrelevant to user voice input 1218 (e.g., when communal device 1204performs natural language processing of user voice input 1218) and onlyprovides the relevant context information to server 1216. In someexamples, communal device 1204 determines what context information isrelevant based on one or more domains of an active ontology (e.g.,ontology 760) that correspond to user voice input 1218 (e.g., byidentifying the context information that is related to or associatedwith the one or more domains corresponding to user voice input 1218). Insome examples, communal device 1204 removes personal information (e.g.,email addresses, home addresses, payment information, or the like)and/or user data (e.g., a user's preferences, media, contacts, speechprofiles, or the like) included in the aggregate context prior toproviding the aggregate context to server 1216. In some examples,communal device 1204 encrypts personal information and/or user dataincluded in the aggregate context prior to providing the aggregatecontext to server 1216 (instead of removing the personal informationand/or user data).

After receiving the data corresponding to user voice input 1218 and theat least a portion of the aggregate context, server 1216 (1) determinesone or more user intents, (2) determines a plurality of taskscorresponding to the one or more user intents, (3) selects twoelectronic devices to perform the plurality of tasks, and (4) generatestwo separate commands (based on the data corresponding to user voiceinput 1218 and context information included in the at least a portion ofthe aggregate context), as described above with reference to FIG. 11 andthe modules of system 1100. Specifically, server 1216 (e.g., deviceselection module 1110) determines that communal device 1204 and communaldevice 1206 are both available, capable of performing at least one taskof the plurality of tasks, and proximate to communal device 1204 (i.e.,the device that provided the data corresponding to user voice input 1218to server 1216 (e.g., to voice input receiver module 1102)). Thus,server 1216 selects communal device 1204 and communal device 1206 formultimodal task performance and assigns a set of tasks to each device(with each set of tasks including at least one tasks of the plurality oftasks). Accordingly, server 1216 (e.g., command module 1112) generates afirst command to perform the first set of tasks and a second command toperform the second set of tasks. The first command is associated with adevice identifier corresponding to communal device 1204, and the secondcommand is associated with a device identifier corresponding to communaldevice 1206. Note, in some examples, one or more tasks of the first setof tasks are identical to one or more tasks of the second set of tasks(e.g., the first set and the second set both include a task ofperforming a search and a task of retrieving data/information based onthe search). Further, in some examples, server 1216 selects more thantwo electronic devices for multimodal task performance (e.g., threeelectronic devices, four electronic devices, or the like) and thusassigns a set of tasks to each of the more than two electronic devicesand generates a separate command to perform each set of tasks.

As represented by arrows 1226, server 1216 transmits the first andsecond commands with their associated device identifiers to communaldevice 1204. In some examples, server 1216 also transmits user data thatwas stored on server 1216 to communal device 1204 (e.g., so thatcommunal device 1204 and/or communal device 1206 may perform one or moretasks based on the user data).

As represented by arrows 1228, after receiving the first and secondcommands with their associated device identifiers, communal device 1204transmits the second command to communal device 1206 based on the deviceidentifier corresponding to communal device 1206 (e.g., based on thestored associations between electronic devices participating incontext-sharing group 1214 and their device identifiers). Further, basedon the device identifier corresponding to communal device 1204 beingassociated with the first command, communal device 1204 determines thatit is to perform the first set of tasks. Thus, after communal device1206 receives the second command, communal device 1204 performs thefirst set of tasks and communal device 1206 performs the second set oftasks. In some examples, communal device 1204 and communal device 1206concurrently perform their respective sets of tasks such that eachdevice concurrently outputs results of the performance of theirrespective set of tasks.

In some examples, the performance of the first set of tasks (by communaldevice 1204) and the second set of tasks (by communal device 1206)causes a division of the audio and visual output of results of theperformance of the tasks between communal device 1204 and communaldevice 1206. For example, if user voice input 1218 is “Hey Siri, show meStar Wars movies”, the first set of tasks and the second set of taskswill each contain the tasks of performing a search for Star Wars moviesand retrieving data/information for the Star Wars movies (e.g., movietitles, year of release, director, and/or the like). However, the firstset of tasks will include a task of outputting the retrieveddata/information within an audio output (e.g., within a digitalassistant response) whereas the second set of tasks will include a taskof outputting the retrieved data/information within a visual audiooutput. Thus, as represented by audio output 1230, after performing thefirst set of tasks, communal device 1204 will, for example, output anaudio digital assistant response (via one or more speakers) thatincludes at least a portion of the retrieved data/information (e.g., “Ifound several Star Wars movies. Star Wars: A New Hope. Star Wars: TheEmpire Strikes Back . . . ”). Further, as represented by resultsinterface 1232, after performing the second set of tasks, communaldevice 906 will, for example, display (on display 1208) an interfaceincluding at least a portion of the retrieved data/information (e.g.,Star Wars movie titles with corresponding images). Although two separatedevices are providing outputs in the above example, the data/informationincluded in the outputs is the same. As such, user 1202 will be able toview the data/information included in interface while listening to thecorresponding data/information included in audio output 1230.Accordingly, the division of audio and visual outputs between at leasttwo electronic devices (as described above) improves a user's digitalassistant experience, as it ensures that a user is able to both view andhear a response to a user request even if the device that initiallyreceives the user request does not, for example, have a display.

In some examples, the performance of the first set of tasks (by communaldevice 1204) and the second set of tasks (by communal device 1206)causes one device to provide a summary response and another device toprovide a more detailed response. For example, if user voice input 1218is “Hey Siri, what is Star Wars?”, the first set of tasks and the secondset of tasks will each contain the tasks of performing a search for StarWars and retrieving data/information associated with Star Wars (e.g.,genre information, creator information, plot information, country oforigin, and/or the like). However, the first set of tasks will include atask of outputting a brief summary of the retrieved data/information,such as outputting short list of data/information and/or a high-leveloverview of the data/information. Thus, as represented by audio output1230, after performing the first set of tasks, communal device 1204will, for example, output an audio digital assistant response (via oneor more speakers) that includes a brief summary of the data/informationretrieved by communal device 1204. In some examples, audio output 1230further directs user 1202 to refer to communal device 1206 for a moredetailed response (e.g., “More information about Star Wars is displayedon your TV.”). As represented by results interface 1232, afterperforming the second set of tasks, communal device 1206 will, forexample, display (on display 1208) an interface including a detailedsummary of the retrieved data/information that includes hyperlinks,images, and/or other information that is not included in the briefsummary output by communal device 1204 (e.g., Star Wars movie titleswith corresponding images, hyperlinks to Star Wars fan pages, links topurchase Star Wars movies, and/or the like). Note, while the aboveexample separates the brief summary and the detailed summary betweenaudio and visual outputs, in some examples, the brief summary and thedetailed summary are both provided as visual outputs (e.g., on displaysof two separate devices). Providing a brief summary and a detailedsummary of retrieved data/information in response to a user request (asdescribed above) improves a user's digital assistant experience, as itensures that a user is able to view and/or hear a brief response to theuser request while having the option to quickly view and/or hear a moredetailed response if the user wants to know more about the topic of therequest (e.g., instead of having to provide a follow-up user request orperform manual searching for more detailed information).

Although not illustrated in FIG. 12A, after communal device 1204provides audio output 1230, communal device 1204 transmits contextinformation to communal device 1206 (e.g., because the provision ofaudio output 1230 is a device state change (e.g., the end of a digitalassistant dialog session)). The context information includes a digitalassistant dialog session history that includes data (e.g., text data)corresponding to audio output 1230, as well as data indicating thedata/information retrieved as a result of the performance of the firstset of tasks. Upon receiving the context information from communaldevice 1204, communal device 1206 incorporates the context informationinto the aggregate context. Similarly, after communal device 1206provides results interface 1232 (via display 1208), communal deviceincorporates its own context information into the aggregate context(e.g., because the provision of results interface 1232 is a device statechange (e.g., the end of a digital assistant response and/oropening/activation of a software application)). The context informationthat communal device incorporates into the aggregate context includesdata indicating the data/information that is displayed in resultsinterface 1232 (e.g., data indicating the results of the performance ofthe second set of tasks). The aggregate context that includes the newcontext information associated with communal device 1204 and communaldevice 1206 is referred to as the “updated aggregate context” in thedescription below.

As shown in FIG. 12B, after communal device 1204 provides audio output1230 and communal device 1206 provides results interface 1232, user 1202provides user voice input 1234, which is received by communal device1204. In the below examples, user voice input 1234 is a user request topurchase media corresponding to a media item (e.g., a representation ofan image, a video, a song, a movie, an e-book, a gaming softwareapplication, or the like) that is included in results interface 1232.For example, if results interface 1232 includes media itemscorresponding to Star Wars movies (or links and/or affordances forpurchasing media), user voice input 1234 may be “Hey Siri, purchase StarWars: The Empire Strikes Back.”

As represented by arrows 1236, in response to receiving user voice input1234 (or, in some examples, in response to detecting a digital assistanttrigger included in user voice input 1234), communal device 1204transmits a request (via network 1212) to communal device 1206 forcommunal device 1206 to transmit an aggregate context of context-sharinggroup 1214 to communal device 1204.

As represented by arrows 1238, after receiving the request for theaggregate context from communal device 1204, communal device 1206transmits the updated aggregate context to communal device 1204. Asdiscussed above, the updated aggregate context includes updated contextinformation associated with communal device 1204 and updated contextinformation associated with communal device 1206.

As represented by arrows 1240, communal device 1204 transmits datacorresponding to user voice input 1234 and at least a portion of theupdated aggregate context to server 1216 (e.g., to voice input receivermodule 1102 and aggregate context receiver module 1104). After receivingthe data corresponding to user voice input 1234 and the at least aportion of the updated aggregate context, server 1216 (1) determines oneor more user intents, (2) determines a plurality of tasks correspondingto the one or more user intents, (3) selects two electronic devices toperform the plurality of tasks, and (4) generates two separate commands(based on the data corresponding to user voice input 1234 and contextinformation included in the at least a portion of the updated aggregatecontext), as described above with reference to FIG. 11 and the modulesof system 1100. Specifically, server 1216 (e.g., device selection module1110) determines that communal device 1206 and user device 1210 are bothavailable, capable of performing at least one task of the plurality oftasks, and proximate to communal device 1204 (i.e., the device thatprovided the data corresponding to user voice input 1234 to server1216). Thus, server 1216 selects communal device 1206 and user device1210 for multimodal task performance and assigns a set of tasks to eachdevice (with each set of tasks including at least one tasks of theplurality of tasks).

Because user voice input 1234 is a user request to purchase media,server 1216 assigns a set of tasks to user device 1210 (referred to asthe third set of tasks) that includes one or more tasks for userauthentication. Further, server 1216 assigns a separate set of tasks tocommunal device 1206 (referred to as the fourth set of tasks) thatincludes one or more tasks for purchasing the requested media.Accordingly, server 1216 (e.g., command module 1112) generates a thirdcommand to perform the third set of tasks and a fourth command toperform the fourth set of tasks. The third command is associated with adevice identifier corresponding to user device 1210, and the fourthcommand is associated with a device identifier corresponding to communaldevice 1206.

Prior to transmitting the third command and the fourth command, server916 (e.g., command module 1112) determines that the third set of tasksincludes one or more tasks for user authentication. Thus, as representedby arrows 1242, server 1216 (1) transmits the third command and thedevice identifier corresponding to user device 1210 to communal device1204 and (2) forgoes transmitting the fourth command and the deviceidentifier corresponding to communal device 1206.

As represented by arrows 1244, after receiving the third command and thedevice identifier corresponding to user device 1210, communal device1204 transmits the third command to user device 1210. The third commandthen causes user device 1210 to perform the third set of tasks,including the one or more tasks for user authentication. For example,the third set of tasks includes outputting a request for a user (e.g.,user 1202) to provide user device 1210 with user authentication data(e.g., voice authentication data, password authentication data, and/orbiometric authentication data (e.g., data corresponding to a face and/ora fingerprint authentication)). In some examples, the request includesuser device 1210 displaying a user authentication interface (e.g., apassword input interface).

In this example, the third set of tasks includes a task of transmittingthe received user authentication data to communal device 1204. Thus, asrepresented by arrows 1246, after user device 1210 receives userauthentication data from a user, user device 1210 transmits the userauthentication data to communal device 1204. Then, as represented byarrows 1248, communal device transmits the user authentication data toserver 1216. Upon receiving the user authentication data, server 1216compares the received user authentication to stored user authenticationdata associated with user device 1210 (e.g., included in stored userdata associated with user device 1210 that was previously synced toserver 1216).

As represented by arrows 1250, if server 1216 determines, based on theabove comparison, that the user that provided the user authenticationdata is authorized to make the requested purchase (e.g., because server1216 determines that the received user authentication data matches thestored user authentication data), server 1216 transmits, to communaldevice 1204, the fourth command and the device identifier correspondingto communal device 1206. Alternatively, if server 1216 determines thatthe user that provided the user authentication data is not authorized tomake the requested purchase (e.g., because server 1216 determines thatthe received user authentication data does not match the stored userauthentication data or because server 1216 determines that storedrestrictions associated with the user (e.g., parental restrictions)prevent the user from making the request purchase), server 1216 forgoestransmitting the fourth command to communal device 1204.

In some examples, the third set of tasks includes a task of locallyauthenticating a user based on received user authentication data insteadof a task of transmitting the received user authentication data tocommunal device 1204. Thus, in these examples, after user device 1210receives user authentication data from a user, user device 1210 comparesthe received user authentication to user authentication data stored onuser device 1210 and determines whether or not the user that providedthe user authentication data is authorized to make the requestedpurchase. If user device 1210 determines that the user is authorized tomake the requested purchase, user device 1210 transmits an indicationthat the user is authorized to make the requested purchase to communaldevice 1204. Communal device 1204 then transmits the indication toserver 1216. In response to receiving the indication, server 1216transmits, to communal device 1204, the fourth command and the deviceidentifier corresponding to communal device 1206.

In some of the examples where the third set of tasks includes a task oflocally authenticating a user based on received user authentication datainstead of a task of transmitting the received user authentication datato communal device 1204, server 1216 concurrently transmits the thirdcommand and the fourth command to communal device 1204. Then, communaldevice transmits the third set of tasks to user device 1210, but forgoestransmitting the fourth command to communal device 1206 until communaldevice 1204 receives the indication that the user is authorized to makethe requested purchase from user device 1210. Thus, communal device 1204will not transmit the fourth command to communal device 1206 if userdevice 1210 determines that the user is not authorized to make therequested purchase.

As represented by arrows 1252, communal device 1204 transmits the fourthcommand to communal device 1206. The fourth command causes communaldevice 1206 to perform the fourth set of tasks, which results incommunal device 1206 purchasing the requested media. In some examples,after purchasing the requested media, communal device 1206 outputs therequested media via display 1208, as represented by media output 1254.Note, while the above examples are directed to purchasing digital media,the above system and process is applicable to other types ofuser-requested purchases, such as purchasing physical items (e.g.,books, groceries, etc.) from a website. Allocating tasks for userauthentication and purchasing to separate electronic devices (asdescribed above) allows a user to quickly and easily provide userauthentication data when, for example, the electronic device that is tomake a user-requested purchase is further away from the user and/or onlyhas less efficient user authentication capabilities (e.g., only performsuser authentication via manual password entry).

Overall, multimodal task performance improves a user's digital assistantexperience because it creates an appearance of a single digitalassistant that is aware of a user's context and surroundings and thatinteracts with the user across multiple devices (as opposed to anindividual digital assistant for each device).

7. System and Technique for a Continuous Digital Assistant Conversationin a Context-Sharing Group

FIG. 13 illustrates a system and technique for continuous digitalassistant conversations across multiple devices participating in acontext-sharing group, according to various examples. As shown in FIG.13, system 1300 includes user device 1304, user device 1306, andcommunal device 1308, all of which are participating in context-sharinggroup 1312 (which is associated with a specific location (e.g., a home,an office, or the like)). User device 1304 and user device 1306 areclient devices (e.g., user device 104, 122, 200, 400, or 600). Forexample, user device 1304 is an iPhone® and user device 1306 is an AppleWatch®. In the examples described below, user device 1304 and userdevice 1306 are registered to user 1302. In some examples, only one ofuser device 1304 and user device 1306 is registered to user 1302.Communal device 1308 is a smart speaker that has the same or similardigital assistant capabilities as user device 1304 and user device 1306.Further, communal device 1308 is the context collector ofcontext-sharing group 1312 (e.g., because communal device 1308 waspreviously elected to be context collector). As discussed above withreference to FIG. 8, communal devices are not registered to a singleuser or are registered to multiple users (e.g., such that the communaldevice may be used by multiple users without additional userregistration and/or user authentication requirements). For example,communal device 1308 is a HomePod®.

System 1300 further includes network 1310 and server 1314 (e.g., DAserver 106). Network 1310 is a wireless communications network (e.g.,network(s) 110). As shown, user device 1304, user device 1306, andcommunal device 1308 communicate with one another and with server 1314via network 1310 (and thus are each connected to network 1310). Server1314 is a remote device that is not participating in context-sharinggroup 1312. In some examples, system 1300 includes one or more otherremote devices (e.g., a local server, a cloud-computing system, or thelike) instead of server 1314. It should be recognized that, in theseexamples, any of the operations performed by user device 1304, userdevice 1306, and/or communal device 1308 can instead be performed byserver 1314. For example, server 1314 can perform the operations of therespective DA client modules (e.g., DA client module 229) of user device1304, user device 1306, and/or communal device 1308.

As shown in FIG. 13, user 1302 provides user voice input 1316 (e.g.,“Hey Siri, what's the temperature in Palo Alto?”), which is received byuser device 1304.

As represented by arrows 1318, in response to receiving user voice input1316 (or, in some examples, in response to detecting a digital assistanttrigger included in user voice input 1316), user device 1304 transmits arequest (via network 1310) to communal device 1308 (i.e., the contextcollector of context-sharing group 1312) for communal device 1308 totransmit an aggregate context of context-sharing group 1312 to userdevice 1304.

As represented by arrows 1320, after receiving the request for theaggregate context from user device 1304, communal device 1308 transmitsthe aggregate context (or, in some examples, at least a portion of theaggregate context) to user device 1304. In some examples, the requestfor the aggregate context causes communal device 1308 to transmit theaggregate context (e.g., data corresponding to the aggregate context),or at least a portion of the aggregate context, to user device 1304. Theaggregate context transmitted to user device 1304 includes contextinformation (e.g., device state change information, contextual stateinformation, device capability information, proximity information,and/or the like) associated with at least user device 1304, user device1306, and communal device 1308 (e.g., because user device 1304, userdevice 1306, and communal device 1308 each recently underwent a devicestate change (e.g., a timer event, detecting a digital assistanttrigger, playing a movie, etc.)). Specifically, the context informationis associated with at least user device 1304, user device 1306, andcommunal device 1308 based on the device identifiers that communaldevice 1308 receives with the context information from at least userdevice 1304, user device 1306, and communal device 1308. In someexamples, the aggregate context does not include any other type ofdevice identification or identifying information other than the deviceidentifiers received with context information included in the aggregatecontext.

In other examples, the aggregate context does include other types ofdevice identifications and/or information identifying a registered userof each electronic device (in addition to the device identifiers). Thisin turn allows server 1314 to determine whether electronic devicesparticipating in a context-sharing group are registered to a single useror two or more different users (as this information may influence thecommands that server 1314 provides). In some examples, deviceidentifications and/or information identifying a registered user of eachelectronic device included in the aggregate context allows server 1314to determine whether or not a user voice input is provided by aregistered. Further, in some examples, server 1314 uses this additionalidentifying information to access and/or utilize user data that isstored on server 1314 and that is associated with one or more of theelectronic devices (e.g., user data that an electronic deviceparticipating in the context-sharing group 1312 previouslysynced/transmitted to the remote devices (e.g., during an automaticand/or periodic user data sync)).

As represented by arrows 1322, after receiving the aggregate contextfrom communal device 1308, user device 1304 transmits data correspondingto user voice input 1316 and at least a portion of the aggregate contextto server 1314.

In some examples, user device 1304 provides audio data corresponding touser voice input 1316 to server 1314. In some examples, user device 1304performs speech-to-text processing of user voice input 1316 (e.g., usingSTT processing module 730) and provides text data corresponding to uservoice input 1316 (e.g., a textual representation of user voice input1316) to server 1314. In some examples, user device 1304 furtherperforms natural language processing of the text data corresponding touser voice input 1316 (e.g., using natural language processing module732) and provides results of the natural language processing (e.g., oneor more user intents) to server 1314.

In some examples, user device 1304 provides all of the aggregate contextto server 1314. In some examples, user device 1304 determines whatcontext information included in the aggregate context is relevant touser voice input 1316 (e.g., when user device 1304 performs naturallanguage processing of user voice input 1316) and only provides therelevant context information to server 1314. In some examples, userdevice 1304 determines what context information is relevant based on oneor more domains of an active ontology (e.g., ontology 760) thatcorrespond to user voice input 1316 (e.g., by identifying the contextinformation that is related to or associated with the one or moredomains corresponding to user voice input 1316). In some examples, userdevice 1304 removes personal information (e.g., email addresses, homeaddresses, payment information, or the like) and/or user data (e.g., auser's preferences, media, contacts, speech profiles, or the like)included in the aggregate context prior to providing the aggregatecontext to server 1314. In some examples, user device 1304 encryptspersonal information and/or user data included in the aggregate contextprior to providing the aggregate context to server 1314 (instead ofremoving the personal information and/or user data).

As represented by arrows 1324, server 1314 transmits, to user device1304, a first command to perform one or more tasks and a deviceidentifier corresponding to user device 1304. After user device 1304receives the first command and determines that it is to perform the oneor more tasks based on the associated device identifier corresponding touser device 1304, user device 1304 performs the one or more tasks. Forexample, if user voice input 1316 is “Hey Siri, what's the temperaturein Palo Alto?”, the one or more tasks include performing a search forweather data associated with Palo Alto, retrieving the requested weatherdata (e.g., temperature data), and generating a digital assistantresponse including the retrieved weather data). The first commandfurther causes user device 1304 to output a digital assistant responsebased on the performance of the one or more tasks. Thus, as shown inFIG. 13, user device 1304 outputs digital assistant response 1326 as anaudio output (e.g., via one or more speakers). Returning to the previousexample, if user voice input 1316 is “Hey Siri, what's the temperaturein Palo Alto?”, digital assistant response 1326 may be “It's currently68 degrees in Palo Alto.”

As represented by arrows 1327, after user device 1304 provides digitalassistant response 1326, user device 1304 transmits context informationto communal device 1308 (e.g., because the output of digital assistantresponse 1326 is a device state change (e.g., the end of a digitalassistant dialog session)). The context information includes a digitalassistant dialog session history that includes data (e.g., text data)corresponding to user voice input 1316 and digital assistant response1326, as well as the data/information retrieved as a result of theperformance of the one or more tasks (e.g., the weather data associatedwith Palo Alto). In some examples, the digital assistant dialog sessionhistory includes data corresponding to a most recent digital assistantdialog session that occurred at user device 1304 (e.g., speechrecognition results, natural language processing results, and/or dataretrieved and/or provided during the most recent digital assistantdialog session (e.g., data corresponding to the most recent user voiceinput and digital assistant response)). In some examples, the digitalassistant dialog session history includes data corresponding to alldigital assistant dialog sessions that have occurred at user device 1304within a predetermined period of time (e.g., within the past hour,within the past day, etc.). After receiving the context information fromuser device 1304, communal device 1308 incorporates the contextinformation into the aggregate context and thus generates an updatedaggregate context that now additionally includes the digital assistantdialog session history that user device 1304 included in its contextinformation.

As shown in FIG. 13, sometime after user device 1304 outputs digitalassistant response 1326, user 1302 moves from a first area (e.g., aliving room, an office, or the like) of the location associated withcontext-sharing group 1312 (e.g., a home of user 1302, an officebuilding where user 1302 works, or the like) where user device 1304 islocated to a second area of the location (e.g., a bedroom, anotheroffice, a different floor of the location, or the like). While at thesecond area of the location, user 1302 provides user voice input 1328(e.g., “Hey Siri, how long will it take me to drive there?” or “HeySiri, how about in New York?”), which is received by user device 1306.In this case, user device 1306 is a wearable user device (e.g., an AppleWatch®) and thus is also located in the second area when it receivesuser voice input 1328. In some examples, user device 1306 is in thefirst area of the location (where user device 1304 is located) when userdevice 1306 receives user voice input 1328.

As represented by arrows 1330, in response to receiving user voice input1328 (or, in some examples, in response to detecting a digital assistanttrigger included in user voice input 1328), user device 1306 transmits arequest to communal device 1308 for communal device 1308 to transmit anaggregate context of context-sharing group 1312 to user device 1306.

As represented by arrows 1332, after receiving the request for theaggregate context from user device 1306, communal device 1308 transmitsthe updated aggregate context (or, in some examples, at least a portionof the updated aggregate context) to user device 1306. As mentionedabove, the updated aggregate context includes the digital assistantdialog session history that user device 1304 provided to communal device1308 (e.g., in addition to other context information associated with oneor more electronic devices participating in context-sharing group 1312that was included in the aggregate context).

As represented by arrows 1334, after receiving the updated aggregatecontext from communal device 1308, user device 1306 transmits datacorresponding to user voice input 1328 and at least a portion of theupdated aggregate context to server 1314. The at least a portion of theupdated aggregate context includes the digital assistant dialog sessionhistory that user device 1304 provided to communal device 1308.

After receiving the data corresponding to user voice input 1328 and theat least a portion of the updated aggregate context, server 1314 (1)determines one or more user intents, (2) determines one or more taskscorresponding to the one or more user intents, (3) selects an electronicdevice to perform the one or more tasks (in this case, user device1306), and (4) generates a command to perform the one or more tasks(based on the data corresponding to user voice input 1328 and contextinformation included in the at least a portion of the updated aggregatecontext), as described above with reference to FIG. 11 and the modulesof system 1100. Specifically, server 1314 uses the data corresponding touser voice input 1316 that is included in the digital assistant dialogsession history (that communal device 1308 added to the updatedaggregate context) to disambiguate user voice input 1328.

In some examples, server 1314 (e.g., task determination module 1108)uses the data corresponding to user voice input 1316 to determine one ormore parameters for the one or more tasks determined based on a userintent corresponding to user voice input 1328. For example, if uservoice input 1328 is “Hey Siri, how long will it take me to drivethere?”, server 1314 will determine a user intent of navigating to alocation. However, user voice input 1328 is ambiguous with respect to alocation parameter for the task of navigation. Thus, server 1314determines a location parameter of “Palo Alto” based on the datacorresponding to user voice input 1316, as “Palo Alto” was the locationparameter for user voice input 1316.

In some examples, server 1314 (e.g., user intent module 1106) uses thedata corresponding to user voice input 1316 to determine a user intentcorresponding to user voice input 1328. For example, if user voice input1328 is “Hey Siri, how about in New York?”, sever 1314 will use the datacorresponding to user voice input 1316 (e.g., text data corresponding touser voice input 1316, natural language processing results correspondingto user voice input 1316, etc.) to determine that user voice input 1328represents a user request for a digital assistant to perform a taskpreviously performed by a digital assistant of user device 1304 usingparameters provided in user voice input 1328 (e.g., a location parameterof “New York”). Thus, if the user intent corresponding to user voiceinput 1316 was a user intent of obtaining weather information (e.g.,because user voice input 1316 was “Hey Siri, what's the temperature inPalo Alto?”), server 1314 will determine that the user intentcorresponding to user voice input 1328 is also obtaining weatherinformation (but with respect to New York instead of Palo Alto).

As represented by arrows 1336, server 1314 transmits, to user device1306, a second command to perform one or more tasks and a deviceidentifier corresponding to user device 1306. After user device 1306receives the second command and determines that it is to perform the oneor more tasks based on the associated device identifier corresponding touser device 1306, user device 1306 performs the one or more tasks. Forexample, if user voice input 1328 is “Hey Siri, how about in New York?”and server 1314 determines that the user intent corresponding to uservoice input 1328 is obtaining weather information (as described above),the one or more tasks will include performing a search for weather dataassociated with New York, retrieving the requested weather data (e.g.,temperature data), and generating a digital assistant response includingthe retrieved weather data). The second command further causes userdevice 1306 to output a digital assistant response based on theperformance of the one or more tasks. Thus, as shown in FIG. 13, userdevice 1306 outputs digital assistant response 1338 as an audio output(e.g., via one or more speakers) and, in some examples, as a visualoutput (e.g., as text) on a display of user device 1306. Returning tothe previous example, if user voice input 1316 is “Hey Siri, how aboutin New York?”, digital assistant response 1338 may be “It's currently 45degrees in New York.”

As represented by arrows 1340, after user device 1306 provides digitalassistant response 1338, user device 1306 transmits context informationto communal device 1308 (e.g., because the output of digital assistantresponse 1338 is a device state change (e.g., the end of a digitalassistant dialog session)). The context information includes a digitalassistant dialog session history that includes data (e.g., text data)corresponding to user voice input 1328 and digital assistant response1338, as well as the data/information retrieved as a result of theperformance of the one or more tasks (e.g., the weather data associatedwith New York). After receiving the context information from user device1306, communal device 1308 incorporates the context information into theupdated aggregate context and thus generates a second updated aggregatecontext that now additionally includes the digital assistant dialogsession history that user device 1306 included in its contextinformation.

8. Processes for Providing a Digital Assistant in a Context-SharingGroup Including at Least Two Electronic Devices

FIGS. 14A-14C illustrate a flow chart representing a process forelecting a context collector of a context-sharing group, according tovarious examples. Process 1400 is performed, for example, using one ormore electronic devices implementing a digital assistant. In someexamples, one or more blocks of process 1400 are performed by one ormore remote devices (e.g., one or more remotes servers (e.g., DA server106), one or more local servers, a cloud-computing system, and/or thelike). For example, the blocks of process 1400 are divided up in anymanner between one or more servers (e.g., DA server 106) and a clientdevice. In other examples, the blocks of process 1400 are divided upbetween one or more servers and multiple client devices (e.g., a mobilephone and a smart watch). Thus, while portions of process 1400 aredescribed herein as being performed by particular devices, it will beappreciated that process 1400 is not so limited. In other examples,process 1400 is performed using only a client device (e.g., user device104) or only multiple client devices. In process 1400, some blocks are,optionally, combined, the order of some blocks is, optionally, changed,and some blocks are, optionally, omitted. In some examples, additionalsteps may be performed in combination with the process 1400.

In some examples, at block 1402, a first electronic device (e.g., apersonal or client electronic device (e.g., a mobile device (e.g.,iPhone®), a tablet computer (e.g., iPad®), a smart watch (e.g., AppleWatch®), a desktop (e.g., iMac®), or a laptop (e.g., MacBook®)) or acommunal electronic device (e.g., a smart TV (e.g., Apple TV®) or asmart speaker (e.g., HomePod®))) (e.g., user device 802) connects to awireless network of a first location (e.g., a local Wi-Fi network (e.g.,of a user's home, office, or the like)) (e.g., as represented by arrow812 of FIG. 8).

In some examples, at block 1404, the first electronic device determineswhether the first electronic device is enrolled in a context-sharinggroup associated with the first location. In some examples, inaccordance with a determination that the first electronic device is notenrolled in the context-sharing group, the first electronic devicerequests enrollments into the context-sharing group. In some examples,the first electronic device must be enrolled in the context-sharinggroup in order to join the context-sharing group (e.g., previouslyenrolled via a software application stored on the first electronicdevice (e.g., HomeKit) or via a website with context-sharing groupfunctionality.

At block 1406, the first electronic device joins the context-sharinggroup (e.g., a collection of one or more electronic devices (e.g.,within a specific location) that automatically share context information(e.g., with a context collector) in response to device state changes)associated with the first location (e.g., as represented bycontext-sharing group 814 of FIG. 8). The context sharing groupassociated with the first location is a collection of at least twoelectronic devices that each share context information with at least oneother electronic device included in the collection. The context sharinggroup includes at least a second electronic device. In some examples,the first electronic device must connect to the wireless network inorder to join the context-sharing group of the firs location. In someexamples, each electronic device participating in the context-sharinggroup is connected to the wireless network. In some examples, the firstelectronic device joins the context-sharing group by establishing acommunication connection (e.g., via which context information and otherdata may be wirelessly transmitted) with at least one other electronicdevice participating in the context-sharing group.

At block 1408, after joining the context-sharing group associated withthe first location, the first electronic device elects (e.g., selects)one electronic device of the collection of at least two electronicdevices as a context collector of the context-sharing group. In someexamples, the first electronic device elects the context collector inresponse to joining the context-sharing group (e.g., immediately afterjoining). In some examples, the first electronic device elects thecontext collector in response to an electronic device participating inthe context-sharing group (e.g., a current context collector) leavingthe context-sharing group (e.g., disconnecting from a wireless networkof the first location).

At block 1410, the first electronic device determines a first contextcollector score corresponding to the first electronic device based atleast on a strength of connectivity between the first electronic deviceand a wireless network of the first location. In some examples, thefirst context collector score is further based on a power source statusof the first electronic device (e.g., wired power connection versusbattery power and/or amount of battery power remaining). In someexamples, the first context collector score is further based on afrequency of movement of the first electronic device in and out of thecontext-sharing group (e.g., a frequency of connecting to/disconnectingfrom the wireless network of the first location).

In some examples, at block 1412, the first electronic device transmitsthe first context collector score to at least the second electronicdevice included in context-sharing group (e.g., as represented by arrows816).

At block 1414, the first electronic device receives, from at least thesecond electronic device, one or more context collector scorescorresponding to at least the second electronic device (e.g., asrepresented by arrows 818 of FIG. 8). In some examples, the firstelectronic device further transmits a context collector indicationindicating whether the first electronic device was previously elected tobe a context collector of the context-sharing group (e.g., when thefirst electronic device previously participated in the context-sharinggroup).

At block 1416, the first electronic device determines based on the firstcontext collector score and the one or more context collector scorescorresponding to at least the second electronic device, which electronicdevice of the electronic devices included in the context-sharing groupto elect as the context collector of the context-sharing group. In someexamples, the first electronic device determines which electronic deviceof the electronic devices included in the context-sharing group to electas the context collector of the context-sharing group includes comparingthe first context collector score to the one or more context collectorscores corresponding to at least the second electronic device, andidentifying, based on the comparison, the highest context collectorscore, wherein an electronic device with the highest context collectorscore is elected to be the context collector.

In some examples, at block 1418, the first electronic device receivesone or more context collector indications from at least the secondelectronic device (e.g., as represented by arrows 818 of FIG. 8). Acontext collector indication indicates whether an electronic device iscurrently the context collector.

In some examples, at block 1420, the first electronic device determineswhether the context-sharing group currently includes a context collectorbased on a context collector indication corresponding to the firstelectronic device and the one or more context collector indicationsreceived from at least the second electronic device.

In some examples, at block 1422, the first electronic device determineswhich electronic device of the electronic devices included in thecontext-sharing group to elect as the context collector of thecontext-sharing group further based on whether the context-sharing groupcurrently includes a context collector.

In some examples, at block 1424, in accordance with a determination thatthe context-sharing group currently includes a context collector, thefirst electronic device elects the current context collector to be thecontext collector of the context-sharing group. In some examples, thesecond electronic device is the context collector of the context-sharinggroup.

In some examples, at block 1426, in accordance with a determination thatthe context-sharing group includes more than one context collector(e.g., because the first electronic device was previously elected to bethe context collector of the context-sharing group when previouslyparticipating in the context-sharing group), determining whichelectronic device of the electronic devices included in thecontext-sharing group to elect as the context collector of thecontext-sharing group based on the first context collector score and theone or more context collector scores corresponding to at least thesecond electronic device.

At block 1428, in accordance with a determination to elect the firstelectronic device as the context collector, the first electronic devicereceives context information (e.g., device state change information(e.g., device state change type, device state change time, and/or thelike), device capability information, contextual state information(e.g., current location, acceleration, display visibility, userattention, and/or the like), user-specific information (e.g.,corresponding to a registered user of an electronic device), and/or thelike) from at least the second electronic device in response to at leastthe second electronic device undergoing a device state change (e.g.,media playback, activation of an application, timer event, alarm event,change in power state (e.g., on/off), change in display visibility(e.g., turning the second electronic device from a display down positionto a display up position (e.g., a display of the second electronicdevice is visible to a user of the second electronic device in thedisplay up position)), digital assistant trigger (e.g., “Hey Siri,”“Siri,” or the like) detection, and/or an end of digital assistantdialog session) (e.g., as represented by alarm event 820 and arrows 822a of FIG. 8).

In some examples, at block 1430, the first electronic device receives arequest for an aggregate context of the context-sharing group (e.g., astored collection of context information received from one or more(e.g., each) electronic devices participating in the context-sharinggroup (e.g., when the one or more electronic devices undergo a devicestate change)) from the second electronic device. In some examples, thesecond electronic device transmits the request to the first electronicdevice in response to receiving a user voice input from a user of thesecond electronic device.

In some examples, at block 1432, the first electronic device transmitsthe aggregate context to the second electronic device. In some examples,transmitting the aggregate context to the second electronic devicecauses the second electronic device to obtain a digital assistantresponse to the user voice input based on context information includedin the aggregate context. In some examples, obtaining the digitalassistant response includes transmitting the user voice input and atleast a portion of the aggregate context to a remote device that is notparticipating in the context-sharing group (e.g., one or more servers, alocal sever, a cloud-computing system, and/or the like) so that theremote device determines the digital assistant response or determinesone or more tasks for the second electronic device to perform. In theexamples where the remote device determines one or more tasks, thesecond electronic device performs the one or more tasks and determinesthe digital assistant response based on results of the performance ofthe one or more tasks.

In some examples, at block 1434, in accordance with a determination toelect the second electronic device as the context collector, the firstelectronic device transmits context information associated with thefirst electronic device to the second electronic device in response tothe first electronic device undergoing a device state change (e.g., asrepresented by alarm event 820 and arrows 822 b of FIG. 8).

FIGS. 15A-15B illustrate a flow chart representing a process forperforming one or more tasks in a context-sharing group, according tovarious examples. Process 1500 is performed, for example, using one ormore electronic devices implementing a digital assistant. In someexamples, one or more blocks of process 1500 are performed by one ormore remote devices (e.g., one or more remotes servers (e.g., DA server106), one or more local servers, a cloud-computing system, and/or thelike). For example, the blocks of process 1500 are divided up in anymanner between one or more servers (e.g., DA server 106) and a clientdevice. In other examples, the blocks of process 1500 are divided upbetween one or more servers and multiple client devices (e.g., a mobilephone and a smart watch). Thus, while portions of process 1500 aredescribed herein as being performed by particular devices, it will beappreciated that process 1500 is not so limited. In other examples,process 1500 is performed using only a client device (e.g., user device104) or only multiple client devices. In process 1500, some blocks are,optionally, combined, the order of some blocks is, optionally, changed,and some blocks are, optionally, omitted. In some examples, additionalsteps may be performed in combination with the process 1500.

At block 1502, a first electronic device (e.g., communal device 904)participating in a context-sharing group associated with a firstlocation receives a user voice input (e.g., “Hey Siri, stop the timer,”Hey Siri, play music,” or the like) (e.g., as represented by user voiceinput 918 of FIG. 9). The context-sharing group is a collection of atleast two electronic devices that each share context information with atleast one other electronic device included in the collection (e.g., asrepresented by context-sharing group 914 of FIG. 9). The collectionincludes at least a second electronic device (e.g., user device 906,user device 910, or communal device 908) and a context collector (e.g.,communal device 908). In some examples, the second electronic device isthe context collector. In some examples, the context collector is athird electronic device that is participating in the context-sharinggroup. In some examples, each electronic device participating in thecontext-sharing group is connected to a single wireless network (e.g., aWi-Fi network) of the first location.

In some examples, at block 1504, in response to receiving the user voiceinput, the first electronic device transmits a request to the contextcollector for the context collector to transmit the aggregate context ofthe context-sharing group to the first electronic device (e.g., asrepresented by arrows 920). The request causes the context collector totransmit the aggregate context to the first electronic device (e.g., asrepresented by arrows 922 of FIG. 9).

At block 1506, the first electronic device receives the aggregatecontext of the context-sharing group from the context collector (e.g., acollection of context information (e.g., device state change information(e.g., type of state change and time of state change), contextual stateinformation (e.g., device location, display visibility (e.g., display upor down), user attention information (e.g., whether a user is looking atthe device display), strength of network connection, amount of batterypower, type of power source (e.g., battery vs wired power source),and/or the like), and/or device capability information (e.g., type ofdevice, processing power, memory availability, display information,speaker information, and/or the like) received from one or more (e.g.,each) electronic devices participating in the context-sharing group)(e.g., as represented by arrows 922 of FIG. 9). In some examples, thecontext information included in the aggregate context indicates whetheran electronic device is available (e.g., whether the electronic deviceis currently being used (e.g., open/active applications), currentlyperforming a task, and/or currently unable to provide an audio and/orvisual output (e.g., because the electronic device is face down)).

In some examples, prior to receiving the aggregate context, at least thefirst electronic device and the second electronic device provide thecontext information included in the aggregate context to the contextcollector. In some examples, the first electronic device and the secondelectronic device each provide their respective context information tothe context collector in response to undergoing a device state change.In some examples, the context information includes device state changeinformation corresponding to at least the first electronic device andthe second electronic device (e.g., data indicating a type of devicestate change and/or a time of device state change). In some examples,the context information includes contextual state information (e.g.,device location, display visibility (e.g., display up or down), userattention information (e.g., whether a user is looking at the devicedisplay), strength of network connection, amount of battery power, typeof power source (e.g., battery vs wired power source), and/or the like)corresponding to at least the first electronic device and the secondelectronic device. In some examples, the context information includesdevice capability information (e.g., type of device, processing power,memory availability, display information, speaker information, and/orthe like) corresponding to at least the first electronic device and thesecond electronic device.

In some examples, at block 1508, prior to transmitting at least aportion of the aggregate context to a remote device that is notparticipating in the context-sharing group (e.g., one or more servers),the first electronic device transmits a request to the second electronicdevice for the second electronic device to provide the first electronicdevice with an indication of whether the second electronic devicedetected (e.g., received or heard) the digital assistant triggerincluded in the user voice input (e.g., a trigger indication). The firstelectronic device transmits the request when the user voice inputincludes a digital assistant trigger (e.g., a word or phrase thatinitiates a dialog session with a digital assistant of an electronicdevice (e.g., “Hey Siri”, “Siri”, or the like). In some examples, thefirst electronic device requests the second electronic device to providethe first electronic device with an indication (e.g., a triggerindication) of whether the second electronic device has detected adigital assistant trigger within a predetermined period of time (e.g.,within the last 2 seconds, 5 seconds, or 10 seconds). In some examples,the first electronic device transmits the request for a triggerindication to each electronic device participating in thecontext-sharing group. In these examples, the request is for eachelectronic device to provide an indication of whether each electronicdevice detected the digital assistant trigger.

In some examples, at block 1510, after receiving the indication from thesecond electronic device (e.g., indicating that the second electronicdevice did or did not detect the digital assistant trigger), the firstelectronic device incorporates the indication into context informationassociated with the second electronic device included in the aggregatecontext (e.g., incorporating the indication as device proximityinformation). After receiving the context information including theindication, a remote device determines a physical proximity of thesecond electronic device to the first electronic device (e.g., whendetermining one or more tasks and/or selecting an electronic device toperform the one or more tasks) based on the indication (e.g., based ondata included in the indication). In some examples, the indicationincludes data indicating an energy level (e.g., decibel level) of thedigital assistant trigger (e.g., the energy level of the digitalassistant trigger when received by the second electronic device). Insome examples, the indication includes a confidence score correspondingto a confidence of the second electronic device that the user voiceinput includes a digital assistant trigger.

At block 1512, the first electronic device provides (e.g., transmits) atleast a portion of the aggregate context and data corresponding to theuser voice input to a remote device that is not participating in thecontext-sharing group (e.g., one or more servers) (e.g., as representedby arrows 924 of FIG. 9).

In some examples, the first electronic device provides all of theaggregate context to the remote device. In some examples, the firstelectronic device determines what context information included in theaggregate context is relevant to the user voice input (e.g., when thefirst electronic device performs natural language processing of thefirst user input) and only provides the relevant context information tothe remote device. In some examples, the first electronic devicedetermines what context information is relevant based on one or moredomains of an active ontology that correspond to the user voice input(e.g., by identifying the context information that is related to the oneor more domains). In some examples, the first electronic device removespersonal data (e.g., personal information and/or user data) included inthe aggregate context prior to providing the aggregate context to theremote device. In some examples, the first electronic device encryptspersonal data (e.g., personal information and/or user data) included inthe aggregate context prior to providing the aggregate context to theremote device.

In some examples, the first electronic device provides audio data to theremote device. In some examples, the first electronic device performsspeech recognition processing (e.g., speech-to-text processing) of theuser voice input and provides text data corresponding to the user voiceinput (e.g., a textual representation of the user voice input) to theremote device. In some examples, the first electronic device performsnatural language processing of the user voice input and provides resultsof the natural language processing (e.g., one or more user intents) tothe remote device.

In some examples, the user voice input is ambiguous with respect todefining the electronic device that is to respond to the user voiceinput (e.g., a user voice input such as “Hey Siri, stop” when an event(e.g., a timer event or alarm event) is occurring at two separateelectronic devices participating in the context-sharing group). In someof these examples, after the remote device (e.g., voice input receivermodule 1102 and aggregate context receiver module 1104 of FIG. 11)receives the data corresponding to the user voice input and the at leasta portion of the aggregate context from the first electronic device, theremote device (e.g., user intent module 1106 of FIG. 11) disambiguatesthe user voice input based on the context information included in the atleast a portion of the aggregate context (e.g., the remote device usesdata indicating a time of device state change included in the aggregatecontext to determine which event began most recently, as that is theevent the user is most likely referring to (and thus the electronicdevice the user is most likely referring to)).

In some examples, the first electronic device and the second electronicdevice are both personal electronic devices (e.g., client devices) thatare each registered to a single user. In some of these examples, afterthe remote device (e.g., voice input receiver module 1102 and aggregatecontext receiver module 1104 of FIG. 11) receives the data correspondingto the user voice input and the at least a portion of the aggregatecontext from the first electronic device, the remote device (e.g., userintent module 1106 of FIG. 11) disambiguates one or more words includedin the user voice input based on user data associated with the secondelectronic device. In some examples, the user data associated with thesecond electronic device includes contacts stored on the secondelectronic device, user speech profiles generated based on user voiceinputs received at the second electronic device, and/or media (e.g.,songs, images, and/or the like) stored on the second electronic device.In some examples, the user data associated with the second electronicdevice is stored on the remote device (e.g., the second electronicdevice periodically syncs the user data to the remote device). In someexamples, the remote device uses user speech profile data associatedwith the second electronic device and/or stored contact informationassociated with the second electronic device to disambiguate the uservoice input (e.g., to recognize one or more words included in the uservoice input).

At block 1514, the first electronic device receives, from the remotedevice, a command to perform one or more tasks (e.g., one or more tasksto be performed by an electronic device of the context-sharing group inorder to fulfill a user intent corresponding to the user voice input)and a device identifier corresponding to the second electronic device(e.g., data indicating the second electronic device) (e.g., asrepresented by arrows 926 of FIG. 9). In some examples, an electronicdevice is assigned a device identifier upon joining the context-sharinggroup. In some examples, the at least a portion of the aggregate contextincludes a device identifier for each electronic device currentlyparticipating in the context-sharing group (e.g., associated with thecontext information for each electronic device). The remote device(e.g., task determination module 1108 and device selection module 1110of FIG. 11) determines the one or more tasks and selects the deviceidentifier based on the data corresponding to the user voice input andcontext information included in the at least a portion of the aggregatecontext.

In some examples, the context-sharing group further includes a fourthelectronic device. In some examples, the first electronic device, thesecond electronic device, and the fourth electronic device are allpersonal electronic devices (e.g., client devices) that are eachregistered to a single user. In some of these examples, at block 1516,prior to transmitting the command to the second electronic device (basedon the device identifier corresponding to the second electronic device),the first electronic device receives, from the remote device, user dataassociated with the fourth electronic device (e.g., the first electronicdevice receives the user data before, at the same time as, or soon afterreceiving the command). In some examples, the user data associated withthe fourth electronic device includes contact information stored on thefourth electronic device and/or media (e.g., songs, images, videos,and/or the like) stored on the fourth electronic device. In someexamples, the user data associated with the fourth electronic device isalso stored on the remote device (e.g., the fourth electronic deviceperiodically syncs the user data to the remote device).

In some examples, the first electronic device and the second electronicdevice are both personal electronic devices (e.g., client devices) thatare each registered to a different user. In some of these examples, atblock 1518, prior to transmitting the command to the second electronicdevice, the first electronic device outputs a request for userauthentication (e.g., voice authentication, password authentication,and/or biometric authentication (e.g., face and/or fingerprintauthentication). In some examples, the first electronic devicedetermines that the second electronic device is registered to adifferent user and, in response to this determination, outputs therequest for user authentication. In some examples, the remote devicedetermines that the first electronic device and the second electronicdevice are each registered to a different user. In these examples, priorto outputting the request for user authentication, the first electronicdevice receives a second command from the remote device and a deviceidentifier corresponding to the first electronic device (e.g., asrepresented by arrows 925 of FIG. 9). The second command then causes thefirst electronic device to output the request for authentication. Insome examples, the second command is received at the same time as thecommand (received at block 1514), and the first electronic deviceexecutes the second command prior to transmitting the command to thesecond electronic device.

In some examples, at block 1520, the first electronic device receivesauthentication data from a user of the first electronic device.

In some examples, at block 1522, after receiving the authenticationdata, the first electronic device transmits the command in response todetermining, based on the received authentication data, that the user ofthe first electronic device is an authorized user of the secondelectronic device. In some examples, the user previously registers withthe second electronic device to become an authorized user of the secondelectronic device. In some examples, a user of the second electronicdevice registers the user of the first electronic device as anauthorized user of the second electronic device. In some examples, theuser of the first electronic device is registered as an authorized userof the second electronic device via a software application stored on thefirst electronic device and/or the second electronic device (e.g.,HomeKit) and/or via a website. In some examples, the first electronicdevice transmits authentication information received from the user tothe remote device (e.g., as represented by arrows 927 of FIG. 9). Inthese examples, the remote device determines that the user is anauthorized user of the second electronic device and thus instructs thefirst electronic device to transmit the command to the second electronicdevice (e.g., via a second command).

At block 1524, the first electronic device transmits the command to thesecond electronic device based on the device identifier (e.g., asrepresented by arrows 928 a or 928 b of FIG. 9). The command causes thesecond electronic device to perform the one or more tasks. In someexamples, the command further causes the second electronic device tooutput (e.g., as an audio output and/or via a display) a user queryafter performing the one or more tasks. In some examples, the user queryasks whether or not to transmit a second command to perform the one ormore tasks to a fourth electronic device that is participating in thecontext-sharing group. In some examples, the command causes the secondelectronic device to output the user query before performing the one ormore tasks.

In some of the examples described above where the first electronicdevice receives (at block 1516) user data associated with a fourthelectronic device, at block 1526, the first electronic device transmitsthe user data associated with the fourth electronic device to the secondelectronic device with the command (e.g., in response to the user voiceinput “Hey Siri, play a Taylor Swift song” the servers provides datacorresponding to a Taylor Swift song stored on the fourth electronicdevice (e.g., audio data) to the first electronic device so that thesecond electronic device can then play the Taylor Swift song despite nothaving the song stored thereon). In these examples, the commandtransmitted to the second electronic device causes the second electronicdevice to perform the one or more tasks based on the user data.

FIGS. 16A-16E illustrate a flow chart representing a process foridentifying an electronic device participating in a context-sharinggroup to perform one or more tasks, according to various examples.Process 1600 is performed, for example, by one or more servers (e.g., DAserver 106). In some examples, process 1600 is performed, for example,by one or more other remote devices, or a combination of remote devices(e.g., one or more local servers, a cloud-computing system, and/or thelike). In some examples, one or more blocks of process 1600 areperformed using one or more electronic devices implementing a digitalassistant. For example, the blocks of process 1600 are divided up in anymanner between one or more servers (e.g., DA server 106) and a clientdevice. In other examples, the blocks of process 1600 are divided upbetween one or more servers and multiple client devices (e.g., a mobilephone and a smart watch). Thus, while portions of process 1600 aredescribed herein as being performed by particular devices, it will beappreciated that process 1600 is not so limited. In other examples,process 1600 is performed using only a client device (e.g., user device104) or only multiple client devices. In process 1600, some blocks are,optionally, combined, the order of some blocks is, optionally, changed,and some blocks are, optionally, omitted. In some examples, additionalsteps may be performed in combination with the process 1600.

At block 1602, one or more servers (e.g., server 916 (e.g., voice inputreceiver module 1102 and aggregate context receiver module 1104 of FIG.11)) receives, from a first electronic device participating in acontext-sharing group associated with a first location (e.g., communaldevice 904), a user voice input and at least a portion of an aggregatecontext of the context-sharing group (e.g., as represented by arrows 924of FIG. 9). The context-sharing group (e.g., context-sharing group 914)is a collection of a plurality of electronic devices that each sharecontext information with at least one other electronic device includedin the collection. In some examples, each electronic device of theplurality of electronic devices is connected to a single wirelessnetwork of the first location (e.g., a Wi-Fi network). In some examples,at least one of the electronic devices participating in thecontext-sharing group is connected to the single wireless network andthe remaining electronic devices participating in the context-sharinggroup are connected to the at least one electronic device via one ormore wireless communication connections (e.g., short distancecommunication connections (e.g., Bluetooth and/or BTLE)).

The aggregate context is, for example, a collection of contextinformation (e.g., device state change information (e.g., type of statechange and time of state change), contextual state information (e.g.,device location, display visibility (e.g., display up or down), userattention information (e.g., whether a user is looking at the devicedisplay), strength of network connection, amount of battery power, typeof power source (e.g., battery vs wired power source), and/or the like),and/or device capability information (e.g., type of device, processingpower, memory availability, display information, speaker information,and/or the like)) received from one or more (e.g., each) electronicdevices participating in the context-sharing group. In some examples,the context information (e.g., device state change information and/orcontextual state information) indicates whether an electronic device isavailable (e.g., whether the electronic device is currently being used(e.g., whether there are open/active applications, etc.), currentlyperforming a task, and/or currently unable to provide an audio and/orvisual output (e.g., because the electronic device is face down, muted,playing media, and/or the like)). In some examples, the contextinformation included in the aggregate context includes device proximityinformation that indicates how physically close one or more electronicdevices participating in the context-sharing group are to the firstelectronic device. In some examples, the device proximity information isbased on data indicating whether or not the one or more electronicdevices participating in the context-sharing group detected (e.g.,heard) a digital assistant trigger word or phrase included in the uservoice input (e.g., data included in one or more trigger indications).

At block 1604, the one or more servers (e.g., user intent module 1106 ofFIG. 11) determine a user intent based on the user voice input. In someexamples, determining the user intent includes the one or more serversperforming speech recognition processing and/or natural languageprocessing of the user voice input. In some examples, the one or moreservers determine the user intent further based on context informationincluded in the at least a portion of aggregate context. In some ofthese examples, the context information includes device state changeinformation (e.g., context information indicating a time, location,and/or type of a device state change for an electronic deviceparticipating in the context-sharing group) associated with a secondelectronic device that is participating in the context-sharing group. Insome examples where the device state change information indicates a typeof device state change and a time of device state change for a mostrecent device state change of the second electronic device, determiningthe user intent includes disambiguating the user voice input based thetype of the device state change and the time of the device state change.For example, if the user voice input is “Hey Siri, stop” and the contextinformation indicates that a timer event is occurring at a device, theone or more servers may determine a user intent of stopping a timerbased on timer event indication. In some examples, when two or moreevents (e.g., timer, alarm, media playback, and/or the like) areoccurring at two or more separate electronic devices, the one or moreservers use device state change time information to determine the userintent based on the most recent device state change (e.g., if a timerevent is more recent than a media playback event, the one or moreservers may determine a user intent of stopping the timer event inresponse to the user voice input “Hey Siri, stop.”).

At block 1606, the one or more servers (e.g., task determination module1108 of FIG. 11) determine one or more tasks corresponding to the userintent (e.g., one or more tasks to be performed by an electronic deviceto fulfill the user intent). In some examples, the one or more taskscorresponding to the user intent are predetermined based on thedetermined user intent. In some examples, the one or more tasks includeperforming a search, retrieving information/data, opening a softwareapplication stored on an electronic device, playing media, making apurchase, displaying retrieved information/data, and/or the like.

At block 1608, the one or more servers (e.g., device selection module1110 of FIG. 11) identify (e.g., select) a second electronic device ofthe plurality of electronic devices (e.g., a personal electronic deviceor a communal electronic device) to perform the one or more tasks basedon the one or more tasks and context information included in the atleast a portion of the aggregate context (e.g., context informationassociated with the second electronic device and/or context informationassociated with one or more electronic devices of the plurality ofelectronic devices). In some examples, the one or more servers identifythe second electronic device further based on the determined userintent. In some examples, the first electronic device is the secondelectronic device (e.g., when the one or more servers identify theelectronic device that provides the user voice input to the one or moreservers as the optimal electronic device to perform the one or moretasks). In some examples, the one or more servers identify two or moreelectronic devices of the plurality of electronic devices instead ofonly one electronic device (e.g., for multimodal task performance).

In some examples, at block 1610, identifying the second electronicdevice (at block 1608) includes the one or more servers determining,based on device state change information included in the contextinformation (e.g., device state change information associated with thesecond electronic device and/or associated with one or more otherelectronic devices of the plurality of electronic devices (e.g., time ofdevice state change, type of device state change (e.g., timer event,alarm event, media playback, or the like), etc.)), whether an event(e.g., a timer event, an alarm event, media playback, and/or the like)that corresponds to the user intent (e.g., a user intent of stopping atimer, stopping an alarm, stopping or updating media playback (e.g.,pausing or changing a song), and/or the like) is currently occurring atone or more electronic devices of the plurality of electronic devices.

In some examples, at block 1612, in accordance with a determination thatan event that corresponds to the user intent is currently occurring onlyat the second electronic device, the one or more servers identify (e.g.,select) the second electronic device.

In some examples, at block 1614, in accordance with a determination thatan event that corresponds to the user intent is currently occurring atthe second electronic device and at least one other electronic device ofthe plurality of electronic devices, the one or more servers determinewhich event began most recently based on data indicating a time ofdevice state change included in the device state change information.

In some examples, at block 1616, in accordance with a determination thatthe event occurring at the second electronic device began most recently,the one or more servers identify (e.g., select) the second electronicdevice.

In some examples, at block 1618, identifying the second electronicdevice (at block 1608) includes the one or more servers determining,based on device state change information included in the contextinformation (e.g., time of device state change, type of device statechange (e.g., timer event, alarm event, media playback, or the like),etc.)), whether an event (e.g., stopping a timer, pausing mediaplayback, and/or the like) that corresponds to the user intent (e.g., auser intent of restarting a timer, resuming media playback, and/or thelike) previously occurred at one or more electronic devices of theplurality of electronic devices within a predetermined period of time(e.g., within the last 5, 10, or 15 minutes).

In some examples, at block 1620, in accordance with a determination thatan event that corresponds to the user intent previously occurred only atthe second electronic device within the predetermined period of time,the one or more servers identify (e.g., select) the second electronicdevice.

In some examples, at block 1622, in accordance with a determination thatan event that corresponds to the user intent previously occurred at thesecond electronic device and at least one other electronic device of theplurality of electronic devices within the predetermined period of time,the one or more servers determine, based on proximity informationincluded in the context information (e.g., proximity informationassociated with the second electronic device and the at least one otherelectronic device), whether the second electronic device or the at leastone other electronic device is physically closer to the first electronicdevice. In some examples, the one or more servers determine whether thesecond electronic device or the at least one other electronic device isphysically closer to the first electronic device based on contextualstate information included in the context information (e.g., a currentlocation of the second electronic device and the at least one otherelectronic device).

In some examples, at block 1624, in accordance with a determination thatthe second electronic device is physically closer to the firstelectronic device than the at least one other electronic device, the oneor more servers identify (e.g., select) the second electronic device. Insome examples, the one or more servers transmit a command to the firstelectronic device (e.g., before, or at the same time as, the command forperforming the one or more tasks) that causes the first electronicdevice to request a user of the first electronic device to select anelectronic device of the plurality of electronic devices to perform theone or more tasks (e.g., instead of determining which electronic deviceis closest to the first electronic device or when the second electronicdevice and the at least one other electronic device are equally asphysically close to the first electronic device (or within a same areaof the first location (e.g., the same room)).

In some examples, the proximity information discussed above is based ondata indicating whether or not one or more electronic devices of theplurality of electronic devices detected a digital assistant triggerincluded in the user voice input (e.g., the data indicating whether ornot the electronic devices detected the digital assistant trigger isincluded in the context information that is included in the aggregatecontext (e.g., included in one or more trigger advertisements that areincluded in the aggregate context)). In some examples, the dataindicating whether or not one or more electronic devices of theplurality of electronic devices detected a digital assistant triggerincluded in the user voice input includes data indicating an energylevel (e.g., decibel level) of the digital assistant trigger (e.g., theenergy level of the digital assistant trigger word or phrase whenreceived by the an electronic device).

In some examples, at block 1626, identifying the second electronicdevice (at block 1608) includes the one or more servers determining,based on device state change information included in the contextinformation (e.g., time of device state change, type of device statechange (e.g., timer event, alarm event, media playback, or the like),etc.)), whether one or more electronic devices of the plurality ofelectronic devices are available to perform the one or more tasks. Forexample, an electronic device is not available if the contextinformation included in the aggregate context (specifically, devicestate change information and/or contextual state information) indicatesthat the electronic device is currently being used (e.g., open/activeapplications), currently performing a task, and/or currently unable toprovide an audio and/or visual output (e.g., because the electronicdevice is face down, muted, playing media, and/or the like). In someexamples, the one or more servers determine whether one or moreelectronic devices are available further based on contextual stateinformation included in the context information (e.g., further based ona display visibility of the one or more electronic devices).

In some examples, at block 1628, in accordance with a determination thatthe second electronic device is available to perform the one or moretasks, the one or more servers determine, based on device capabilityinformation included in the context information (e.g., device capabilityinformation associated with the second electronic device (e.g., type ofdevice, processing power, memory availability, display information,speaker information, and/or the like)), whether the second electronicdevice is capable of performing the one or more tasks. For example, ifthe one or more tasks include the task of displaying information (e.g.,results of the task performance), then an electronic device must atleast have a display in order to be capable of performing the one ormore tasks. In some examples, the one or more servers determine whetherthe second electronic device is capable of performing the one or moretasks further based on contextual state information included in thecontext information (e.g., contextual state information associated withthe second electronic device, such as strength of network connection,amount of battery power, type of power source (e.g., battery vs wiredpower source), and/or the like).

In some examples, at block 1630, in accordance with a determination thatthe second electronic device is capable of performing the one or moretasks, the one or more servers determine whether at least one otherelectronic device of the plurality of electronic devices is availableand capable of performing the one or more tasks.

In some examples, at block 1632, in accordance with a determination thatno other electronic device of the plurality of electronic devices isavailable and capable of performing the one or more tasks, the one ormore servers identify (e.g., select) the second electronic device.

In some examples, at block 1634, in accordance with a determination thatat least one other electronic device of the plurality of electronicdevices is available and capable of performing the one or more tasks,the one or more servers determine, based on proximity informationincluded in the context information (e.g., proximity informationassociated with the second electronic device and the at least one otherelectronic device), whether the second electronic device or the at leastone other electronic device is physically closer to the first electronicdevice. The proximity information is based on data indicating whether ornot one or more electronic devices of the plurality of electronicdevices detected a digital assistant trigger included in the user voiceinput (e.g., data included in one or more trigger indications). The dataindicating whether or not one or more electronic devices of theplurality of electronic devices detected a digital assistant triggerincluded in the user voice input includes data indicating a first energylevel of the digital assistant trigger according to the secondelectronic device and data indicating a second energy level of thedigital assistant trigger according to the at least one other electronicdevice. In some examples, the one or more servers determine whether thesecond electronic device or the at least one other electronic device isphysically closer to the first electronic device further based oncontextual state information included in the context information (e.g.,a current location of the second electronic device and a currentlocations of the at least one other electronic device).

In some examples, at block 1636, determining whether the secondelectronic device or the at least one other electronic device isphysically closer to the first electronic device (at block 1634)includes the one or more servers comparing a first energy level of thedigital assistant trigger according to the second electronic device to asecond energy level of the digital assistant trigger according to the atleast one other electronic device.

In some examples, at block 1638, the one or more servers determinewhether a difference between the first energy level and the secondenergy level is less than a predetermined threshold (e.g., apredetermined decibel level difference (e.g., 2 decibels, 5 decibels, orthe like)).

In some examples, at block 1640, in accordance with a determination thatthe difference is less than the predetermined threshold, the one or moreservers determine, based on user attention information included in thecontext information, whether a user of the first electronic device islooking at a display of the second electronic device or at a display ofthe at least one other electronic device.

In some examples, at block 1642, in accordance with a determination thatthe user is looking at the display of the second electronic device, theone or more servers identify (e.g., select) the second electronicdevice.

In some examples, at block 1642, in accordance with a determination thatthe second electronic device is physically closer to the firstelectronic device than the at least one other electronic device (atblock 1634), the one or more servers identify (e.g., select) the secondelectronic device.

In some examples, at block 1646, the one or more severs identify (e.g.,select), based on the one or more tasks and the context information, athird electronic device of the plurality of electronic devices toperform at least one task (e.g., displaying retrieved information/data,providing an audio output based on retrieved information/data, and/orthe like) of the one or more tasks (e.g., before, after, or concurrentlywith the second electronic device's performance of the remaining tasks).

At block 1648, the one or more servers (e.g., command module 1112)transmit, to the first electronic device, a command to perform the oneor more tasks and a device identifier corresponding to the secondelectronic device (e.g., data indicating the second electronic device)(e.g., as represented by arrows 926 of FIG. 9). After receiving thecommand, the first electronic device transmits the command to the secondelectronic device based on the device identifier. The command thencauses the second electronic device to perform the one or more tasks. Insome examples, the command further causes the second electronic deviceto provide an audio and/or visual digital assistant response based onthe performance of the one or more tasks (e.g., “Now playing TaylorSwift” or “Resuming Star Wars: The Empire Strikes Back.”).

In some examples, an electronic device is assigned a device identifierupon joining the context-sharing group. In some examples, the at least aportion of the aggregate context includes a device identifier for eachelectronic device currently participating in the context-sharing group(e.g., associated with the context information for each electronicdevice).

In some of the examples described above where the one or more serversidentify a third electronic device to perform at least one task of theone or more tasks (at block 1646), at block 1650, the one or moreservers transmit, to the first electronic device, a second command toperform the at least one task and a device identifier corresponding tothe third electronic device. In some examples, the one or more serversconcurrently transmit the command and the second command to the firstelectronic device.

FIGS. 17A-17C illustrate a flow chart representing a process formultimodal task performance in a context-sharing group, according tovarious examples. Process 1700 is performed, for example, using one ormore electronic devices implementing a digital assistant. In someexamples, one or more blocks of process 1700 are performed by one ormore remote devices (e.g., one or more remotes servers (e.g., DA server106), one or more local servers, a cloud-computing system, and/or thelike). For example, the blocks of process 1700 are divided up in anymanner between one or more servers (e.g., DA server 106) and a clientdevice. In other examples, the blocks of process 1700 are divided upbetween one or more servers and multiple client devices (e.g., a mobilephone and a smart watch). Thus, while portions of process 1700 aredescribed herein as being performed by particular devices, it will beappreciated that process 1700 is not so limited. In other examples,process 1700 is performed using only a client device (e.g., user device104) or only multiple client devices. In process 1700, some blocks are,optionally, combined, the order of some blocks is, optionally, changed,and some blocks are, optionally, omitted. In some examples, additionalsteps may be performed in combination with the process 1700.

At block 1702, a first electronic device participating in acontext-sharing group associated with a first location (e.g., communaldevice 1204) receives a user voice input (e.g., user voice input 1218).The context-sharing group is a collection of a plurality of electronicdevices that each share context information with at least one otherelectronic device included in the collection. The collection includes acontext collector (e.g., communal device 1206).

At block 1704, the first electronic device receives, from the contextcollector, an aggregate context of the context-sharing group (e.g., asrepresented by arrows 1222 of FIG. 12A).

At block 1706, after receiving the aggregate context, the firstelectronic device provides at least a portion of the aggregate contextand data corresponding to the user voice input to a remote device thatis not participating in the context-sharing group (e.g., as representedby arrows 1224 of FIG. 12A). The remote device determines a plurality oftasks based on the data corresponding to the user voice input (e.g., aplurality of tasks to be performed by one or more electronic devicesparticipating in the context-sharing group in order to fulfill a userintent corresponding to the user voice input). In some examples, theremote device determines the plurality of tasks further based on contextinformation included in the at least a portion of the aggregate context(e.g., further based on device state change information).

In some examples, the first electronic device provides all of theaggregate context to the remote device. In some examples, the firstelectronic device determines what context information included in theaggregate context is relevant to the user voice input (e.g., when thefirst electronic device performs natural language processing of thefirst user input) and only provides the relevant context information tothe remote device. In some examples, the first electronic devicedetermines what context information is relevant based on one or moredomains of an active ontology that correspond to the user voice input(e.g., by identifying the context information that is related to the oneor more domains). In some examples, the first electronic device removespersonal data (e.g., personal information and/or user data) included inthe aggregate context prior to providing the aggregate context to theremote device. In some examples, the first electronic device encryptspersonal data (e.g., personal information and/or user data) included inthe aggregate context prior to providing the aggregate context to theremote device.

At block 1708, the first electronic device receives, from the remotedevice, a first command to perform a first set of tasks of the pluralityof tasks and a second command to perform a second set of tasks of theplurality of tasks (e.g., as represented by arrows 1226 of FIG. 12A). Insome examples, one or more tasks of the first set of tasks are identicalto one or more tasks of the second set of tasks (e.g., performing asearch, retrieving information/data based on the search, opening asoftware application stored on the first and second electronic devices,and/or the like).

In some examples, the at least a portion of the aggregate contextincludes context information associated with the second electronicdevice and context information associated with a third electronic deviceof the plurality of electronic devices. In some of these examples, theremote device determines the first set of tasks based on devicecapability information included the context information associated withthe second electronic device (e.g., whether the second electronic devicehas a display and/or a size of the display, whether the secondelectronic device has a speaker and/or a loudness of the speaker, deviceprocessing power, and/or the like), and the remote device determines thesecond set of tasks based on device capability information included thecontext information associated with the third electronic device (e.g.,whether the third electronic device has a display and/or a size of thedisplay, whether the third electronic device has a speaker and/or aloudness of the speaker, device processing power, and/or the like).Further, in some of these examples, the remote device determines thefirst set of tasks and the second set of tasks in response todetermining, based on the context information associated with the secondelectronic device and the context information associated with the thirdelectronic device, that the second electronic device and the thirdelectronic device are both available (e.g., not currently being used(e.g., open/active applications), not currently performing a task,and/or currently able to provide an audio and/or visual output (e.g.,because the electronic device is face up)), capable of performing atleast one task of the plurality of tasks, and proximate to the firstelectronic device (e.g., located within a same area of the firstlocation (e.g., the same room) as the first electronic device. In someexamples, the remote device determines whether an electronic device islocated within a same area of the first location as the first electronicdevice based on proximity information included in the contextinformation (e.g., based on an energy level (e.g., decibel level) of thedigital assistant trigger word or phrase according to the secondelectronic device and the third electronic device, respectively (e.g.,the energy level of the digital assistant trigger word or phrase whenreceived by the second electronic device compared to the energy level ofthe digital assistant trigger word or phrase when received by the thirdelectronic device).

At block 1710, the first electronic device receives, from the remotedevice, a first device identifier corresponding to a second electronicdevice of the plurality of electronic devices (e.g., data indicating thesecond electronic device) and a second device identifier correspondingto a third electronic device of the plurality of electronic devices(e.g., as represented by arrows 1226 of FIG. 12A). In some examples, thesecond electronic device or the third electronic device is the firstelectronic device.

At block 1712, the first electronic device transmits the first commandto the second electronic device based on the first device identifier(e.g., as represented by arrows 1228 of FIG. 12A). The first commandcauses the second electronic device to perform the first set of tasks.As mentioned above, in some examples, the first electronic device is thesecond electronic device. In these examples, the first electronic deviceperforms the first set of tasks in response to receiving the firstcommand from the remote device (instead of transmitting the firstcommand).

At block 1714, the first electronic device transmits the second commandto the third electronic device based on the second device identifier.The second command causes the third electronic device to perform thesecond set of tasks. As mentioned above, in some examples, the firstelectronic device is the third electronic device. In these examples, thefirst electronic device performs the second set of tasks in response toreceiving the second command from the remote device (instead oftransmitting the second command).

In some examples, the second electronic device only outputs an audiooutput based on the performance of the first set of tasks (e.g., adigital assistant response naming the titles of all Star Wars movies),and the third electronic device only displays a visual output based onthe performance of the second set of tasks (e.g., displays the titles ofthe Star Wars movies with corresponding movie poster images).

In some examples, in response to performing the first set of tasks, thesecond electronic device outputs (e.g., on a display of the secondelectronic device and/or as an audio output) a brief summary of data orinformation retrieved based on the performance of the first set of tasks(e.g., a brief summary of text, hyperlinks, images, and/or the likecorresponding to Star Wars movie titles, historical information, castinformation, and/or the like).

In some examples, in response to performing the second set of tasks, thethird electronic device outputs (e.g., on a display of the thirdelectronic device and/or as an audio output) a detailed summary of dataor information retrieved based on the performance of the second set oftasks (e.g., a detailed summary of text, hyperlinks, images, and/or thelike corresponding to Star Wars movie titles, historical information,cast information, and/or the like). In some examples, the detailedsummary includes at least one of hyperlinks, images, audio data, or textdata that is not included in the brief summary.

In some examples, at block 1716, the first electronic device receives asecond user voice input (e.g., user voice input 1234) representing auser request to make a purchase (e.g., “Hey Siri, purchase Star Wars:The Empire Strikes Back.”).

In some examples, at block 1718, the first electronic device receives,from the context collector, an updated aggregate context (e.g., asrepresented by arrows 1238 of FIG. 12B). The updated aggregate contextincludes updated context information associated with the secondelectronic device and updated context information associated with thethird electronic device (e.g., the updated context information for bothdevices include data indicating results of the performance of the firstset of tasks and results of the performance of the second set of tasks,respectively (e.g., any audio output that was provided, what iscurrently displayed, etc.)). In some examples, the second electronicdevice transmits the updated context information associated with thesecond electronic to the context collector after performing the firstset of tasks, and the third electronic device transmits the updatedcontext information associated with the third electronic to the contextcollector after performing the second set of tasks

In some examples, at block 1720, the first electronic device transmits,to the remote device, data corresponding to the second user voice inputand at least a portion of the updated aggregate context (e.g., asrepresented by arrows 1240 of FIG. 12B). The remote device thendetermines a second plurality of tasks based on the data correspondingto the second user voice input. In some examples, the remote devicedetermines the plurality of tasks further based on context informationincluded in the at least a portion of the updated aggregate context(e.g., further based on device state change information).

In some examples, at block 1722, the first electronic device receives,from the remote device, a third command to perform a third set of tasksof the second plurality of tasks and a third device identifiercorresponding to a fourth electronic device of the plurality ofelectronic devices (e.g., as represented by arrows 1242 of FIG. 12B).The third set of tasks includes a task of user authentication. In someexamples, the fourth electronic device is the second electronic device.

In some examples, at block 1724, the first electronic device transmitsthe third command to the fourth electronic device based on the thirddevice identifier (e.g., as represented by arrows 1244 of FIG. 12B). Thethird command causes the fourth electronic device to perform the thirdset of tasks.

In some examples, after transmitting the third command to the fourthelectronic device (at block 1724), at block 1726, the first electronicdevice receives, from the fourth electronic device, user authenticationdata corresponding to a user of the first electronic device (e.g., voiceauthentication data, password authentication data, and/or biometricauthentication data (e.g., data corresponding to a face and/or afingerprint authentication)) (e.g., as represented by arrows 1246 ofFIG. 12B).

In some examples, at block 1728, the first electronic device transmitsthe user authentication data to the remote device (e.g., as representedby arrows 1248 of FIG. 12B).

In some examples, at block 1730, the first electronic device receives,from the remote device, a fourth command to perform a fourth set oftasks of the second plurality of tasks and the second device identifiercorresponding to the third electronic device (e.g., as represented byarrows 1250 of FIG. 12B). The remote device transmits the fourth commandto the first electronic device in response to determining, based on theuser authentication data, that the user of the first electronic deviceis authorized to make the requested purchase. The fourth set of tasksincludes a task of performing the requested purchase. In some examples,the remote device transmits the fourth command before, at the same timeas, or soon after the third command. In these examples, the firstelectronic device does not transmit the fourth command to the thirdelectronic device until the remote device informs the first electronicdevice that the user of the first electronic device is authorized tomake the requested purchase).

In some examples, at block 1732, the first electronic device transmitsthe fourth command to the third electronic device based on the seconddevice identifier (e.g., as represented by arrows 1252 of FIG. 12B). Thefourth command causes the third electronic device to perform the fourthset of tasks.

In some examples, after transmitting the third command to the fourthelectronic device (at block 1724), at block 1734, the first electronicdevice receives, from the fourth electronic device, an indication that auser of the first electronic device is authorized to make the requestedpurchase (e.g., the fourth electronic device locally authenticates theuser (e.g., based on user authentication data stored on the fourthelectronic device) and transmits the indication in response to theauthentication).

In some examples, at block 1736, the first electronic device transmitsthe indication to the remote device.

In some examples, at block 1738, the first electronic device receives,from the remote device, a fifth command to perform a fifth set of tasksof the second plurality of tasks and the second device identifiercorresponding to the third electronic device. The remote devicetransmits the fifth command to the first electronic device in responseto receiving the indication that the user of the first electronic deviceis authorized to make the requested purchase. The fifth set of tasksincludes a task of performing the requested purchase.

In some examples, the remote device transmits the fifth command before,at the same time as, or soon after the third command. In these examples,the first electronic device does not transmit the fifth command to thethird electronic device until the first electronic device receives theindication that the user of the first electronic device is authorized tomake the requested purchase (in this manner, the servers are notinvolved in the user authentication decision). If the user is notauthorized to make the requested purchase, the first electronic devicedoes not transmit the fifth command to the third electronic device.

In some examples, at block 1740, the first electronic device transmitsthe fifth command to the third electronic device based on the seconddevice identifier. The fifth command causes the third electronic deviceto perform the fifth set of tasks.

FIGS. 18A-18B illustrate a flow chart representing a process for acontinuous digital assistant conversation across multiple electronicdevices participating in a context-sharing group, according to variousexamples. Process 1800 is performed, for example, using one or moreelectronic devices implementing a digital assistant. In some examples,one or more blocks of process 1800 are performed by one or more remotedevices (e.g., one or more remotes servers (e.g., DA server 106), one ormore local servers, a cloud-computing system, and/or the like). Forexample, the blocks of process 1800 are divided up in any manner betweenone or more servers (e.g., DA server 106) and a client device. In otherexamples, the blocks of process 1800 are divided up between one or moreservers and multiple client devices (e.g., a mobile phone and a smartwatch). Thus, while portions of process 1800 are described herein asbeing performed by particular devices, it will be appreciated thatprocess 1800 is not so limited. In other examples, process 1800 isperformed using only a client device (e.g., user device 104) or onlymultiple client devices. In process 1800, some blocks are, optionally,combined, the order of some blocks is, optionally, changed, and someblocks are, optionally, omitted. In some examples, additional steps maybe performed in combination with the process 1800.

At block 1802, a first electronic device participating in acontext-sharing group associated with a first location (e.g., userdevice 1304) receives a first user voice input (e.g., user voice input1316 of FIG. 13 (e.g., “Hey Siri, what's the temperature in PaloAlto?”)). The context-sharing group is a collection of at least twoelectronic devices that each share context information with at least oneother electronic device included in the collection. The collectionincludes a second electronic device (e.g., user device 1306) and acontext collector (e.g., communal device 1308). In some examples, thecontext collector is a third electronic device that is participating inthe context-sharing group. In some examples, the context collector isthe first electronic device or the second electronic device. In someexamples, the first electronic device and the second electronic deviceare located within two separate areas (e.g., two separate rooms) of thefirst location.

In some examples, at block 1804, prior to outputting a first digitalassistant response, the first electronic receives an aggregate contextof the context-sharing group from the context collector (e.g., asrepresented by arrows 1320 of FIG. 13). In these examples, the aggregatecontext includes context information associated with the firstelectronic device and context information associated with the secondelectronic device.

In some examples, at block 1806, the first electronic device transmitsdata corresponding to the first user voice input and at least a portionof the aggregate context to a remote device that is not participating inthe context-sharing group (e.g., one or more remote servers, one or morelocal servers, a cloud-computing system, and/or the like) (e.g., asrepresented by arrows 1322 of FIG. 13).

In some examples, at block 1808, the first electronic device receives afirst command to perform one or more tasks and a first device identifiercorresponding to the first electronic device from the remote device(e.g., as represented by arrows 1324 of FIG. 13). In these examples, theremote device determines the one or more tasks and the device identifiercorresponding to the first electronic device based at least on the datacorresponding to the first user voice input and context informationincluded in the aggregate context (e.g., the context informationassociated with the first electronic device and/or context informationassociated with one or more other electronic devices participating inthe context-sharing group). The first command causes the firstelectronic device to perform the one or more tasks and determine a firstdigital assistant response based on results of the performance of theone or more tasks.

At block 1810, the first electronic device outputs a first digitalassistant response based on the first user voice input (e.g., digitalassistant response 1326 (e.g., “It's currently 68 degrees in PaloAlto.”)).

After outputting the first digital assistant response (e.g., immediatelyafter or several second after (e.g., after the current dialog sessionhas ended (e.g., 1 or 2 seconds after the first electronic deviceprovides the first digital assistant response with no additional uservoice inputs received at the first electronic device))), at block 1812,the first electronic device transmits context information including adigital assistant dialog session history for the first electronic deviceto the context collector (e.g., as represented by arrows 1327 of FIG.13). In some examples, the digital assistant dialog session historyincludes data corresponding to a most recent digital assistant dialogsession (e.g., ASR results, NLP results, and/or data retrieved and/orprovided during the most recent digital assistant dialog session (e.g.,data corresponding to the most recent user voice input and digitalassistant response)). For example, the digital assistant dialog sessionhistory includes data corresponding to the first user voice input andthe first digital assistant response. In some examples, the digitalassistant dialog session history includes data corresponding to digitalassistant dialog sessions that have occurred within a predeterminedperiod of time (e.g., within the past hour, within the past day, etc.).

At block 1814, the second electronic device receives a second user voiceinput (e.g., user voice input 1328 (e.g., “Hey Siri, how long will ittake me to drive there?”)). In some examples, the first electronicdevice and the second electronic device receive the first user voiceinput and the second user voice input from a single user. In otherexamples, the first electronic device and the second electronic devicereceive the first user voice input and the second user voice input fromdifferent users.

In some examples, at block 1816, the second electronic device transmitsa request for an updated aggregate context of the context-sharing groupto the context collector (e.g., as represented by arrows 1330 of FIG.13). In some examples, the second electronic device transmits therequest for the updated aggregate context in response to receiving thesecond user voice input.

At block 1818, the second electronic device receives an updatedaggregate context of the context-sharing group from the contextcollector (e.g., as represented by arrows 1332 of FIG. 13). The updatedaggregate context includes the digital assistant dialog session historyfor the first electronic device. In some examples, the context collectorgenerates the updated aggregate context (e.g., in response to receivingthe context information from the first electronic device). In theseexamples, generating the updated aggregate context includes the contextcollector updating context information associated with the firstelectronic device included in an aggregate context of thecontext-sharing group based at least on the digital assistant dialogsession history for the first electronic device.

In some examples, at block 1820, prior to the second electronic deviceoutputting a second digital assistant response, the second electronicdevice transmits data corresponding to the second user voice input andat least a portion of the updated aggregate context to a remote devicethat is not participating in the context-sharing group (e.g., one ormore remote servers, one or more local servers, a cloud-computingsystem, and/or the like) (e.g., as represented by arrows 1334 of FIG.13). In these examples, the at least a portion of the updated aggregatecontext includes the digital assistant dialog session history for thefirst electronic device.

In some examples, at block 1822, the second electronic device receives asecond command to perform one or more tasks and a second deviceidentifier corresponding to the second electronic device from the remotedevice (e.g., the device identifier causes the second electronic deviceto perform the one or more tasks) (e.g., as represented by arrows 1336of FIG. 13). The remote device (e.g., user intent module 1106 and/ortask determination module 1108 of FIG. 11) determines the one or moretasks and the device identifier corresponding to the second electronicdevice based at least on the data corresponding to the second user voiceinput and the digital assistant dialog session history for the firstelectronic device. The second command causes the second electronicdevice to perform the one or more tasks and determine the second digitalassistant response based on results of the performance of the one ormore tasks.

In some examples, the digital assistant dialog session history for thefirst electronic device includes data corresponding to the first uservoice input. In these examples, determining the one or more tasks basedat least on the data corresponding to the second user voice input andthe digital assistant dialog session history for the first electronicdevice includes the remote device disambiguating the second user voiceinput based on the first user voice input. In some examples,disambiguating the second user voice input based on the first user voiceinput includes the remote device (e.g., task determination module 1108)determining one or more parameters for the second user voice input basedon one or more parameters of the first user voice input (e.g., alocation, contact name, website, email address, etc. included in thefirst user voice input). In some examples, disambiguating the seconduser voice input (e.g., “Hey Siri, how about in New York?”) includes theremote device (e.g., user intent module 1106) determining that thesecond user voice input represents a user request for a digitalassistant to perform a task previously performed by the digitalassistant of the first electronic device (e.g., weather determination)using parameters provided in the second user voice input (e.g., alocation (“New York”), contact name, website, email address, etc.included in the second user voice input).

At block 1824, the second electronic device outputs a second digitalassistant response based on the second user voice input and the digitalassistant dialog session history for the first electronic device (e.g.,digital assistant response 1338 of FIG. 13 (e.g., “Traffic to Palo Altois light, so I'm estimating 15 minutes via El Camino Real.”)).

FIGS. 19A-19B illustrate a flow chart representing a process forsuppressing a delayed digital assistant trigger detection using acontext collector of a context-sharing group, according to variousexamples. Process 1900 is performed, for example, using one or moreelectronic devices implementing a digital assistant. In some examples,one or more blocks of process 1900 are performed by one or more remotedevices (e.g., one or more remotes servers (e.g., DA server 106), one ormore local servers, a cloud-computing system, and/or the like). Forexample, the blocks of process 1900 are divided up in any manner betweenone or more servers (e.g., DA server 106) and a client device. In otherexamples, the blocks of process 1900 are divided up between one or moreservers and multiple client devices (e.g., a mobile phone and a smartwatch). Thus, while portions of process 1900 are described herein asbeing performed by particular devices, it will be appreciated thatprocess 1900 is not so limited. In other examples, process 1900 isperformed using only a client device (e.g., user device 104) or onlymultiple client devices. In process 1900, some blocks are, optionally,combined, the order of some blocks is, optionally, changed, and someblocks are, optionally, omitted. In some examples, additional steps maybe performed in combination with the process 1900.

At block 1902, a first electronic device participating in acontext-sharing group associated with a first location (e.g., userdevice 1006 of FIG. 10) receives a user voice input (e.g., user voiceinput 1014 of FIG. 10). The user voice input includes a digitalassistant trigger (e.g., a word or phrase that initiates a dialogsession with a digital assistant of an electronic device (e.g., “Hey Sin. . . ”, “Siri”, or the like)). The context-sharing group is acollection of at least two electronic devices that each share contextinformation with at least one other electronic device participating inthe collection. The collection includes at least a second electronicdevice (e.g., communal device 1004) and a context collector (e.g.,communal device 1008). In some examples, the second electronic device isthe context collector. In some examples, the context collector is athird electronic device participating in the context-sharing group. Insome examples, each electronic device participating in thecontext-sharing group is connected to a single wireless network of thefirst location.

At block 1904, in response to detecting the digital assistant trigger(e.g., determining that the user voice input includes the digitalassistant trigger), the first electronic device transmits a firsttrigger advertisement to the context collector (e.g., via a wirelessnetwork of the first location) (e.g., as represented by arrows 1022 ofFIG. 10). The first trigger advertisement indicates a first time atwhich the digital assistant trigger ended according to the firstelectronic device. In some examples, the first trigger advertisementincludes data indicating an energy level (e.g., decibel level) of thedigital assistant trigger word or phrase (e.g., the energy level of thedigital assistant trigger word or phrase when received by the firstelectronic device). In some examples, the first trigger advertisementincludes a confidence score corresponding to a confidence of the firstelectronic device that the user voice input includes a digital assistanttrigger word or phrase.

In some examples, the first electronic device and the second electronicdevice share a short distance communication connection (e.g., aBluetooth or Bluetooth Low Energy (BTLE) connection). In some of theseexamples, at block 1906, in response to detecting the digital assistanttrigger, the first electronic device transmits the first triggeradvertisement to the second electronic device via the short distancecommunication connection (e.g., the first electronic device transmitsthe first trigger advertisements via Bluetooth or BTLE before, at thesame time as, or soon after transmitting the first trigger advertisementto the context collector).

At block 1908, the first electronic device receives, from the contextcollector, a second trigger advertisement (e.g., as represented byarrows 1024 of FIG. 10). The second trigger advertisement indicates asecond time at which the digital assistant trigger ended according tothe second electronic device. In some examples, the second electronicdevice transmits the second trigger advertisement to the contextcollector in response to detecting the digital assistant triggerincluded in the user voice input (before the context collector transmitsthe second trigger advertisement to the first electronic device). Insome examples, the second electronic device includes the second triggeradvertisement (e.g., data corresponding to the second triggeradvertisement) in context information that the second electronic devicetransmits to the context collector after detecting the digital assistanttrigger included in the user voice input (e.g., as represented by arrows1016 of FIG. 10).

In some of the examples where the first electronic device and the secondelectronic device share a short distance communication connection (e.g.,described above with reference to block 1906), at block 1910, the firstelectronic device receives a third trigger advertisement from the secondelectronic device via the short distance communication connection. Thethird trigger advertisement indicates a third time at which the digitalassistant trigger ended according to the second electronic device. Insome examples, the third time is identical to the second time indicatedby the second trigger advertisement. In some examples, the secondelectronic device transmits the third trigger advertisement via theshort distance communication connection in response to receiving thefirst trigger advertisement from the first electronic device via theshort distance communication connection.

At block 1912, the first electronic device determines whether the secondtime is within a predetermined time range (e.g., 750 milliseconds, 500milliseconds, 100 milliseconds, or the like) before the first time(e.g., determining whether the second trigger advertisement is “sane”).

In some of the examples where the first electronic device and the secondelectronic device share a short distance communication connection (e.g.,described above with reference to blocks 1906 and 1910), at block 1914,after determining whether the second time is within the predeterminedtime range before the first time, the first electronic device determineswhether the third time is within the predetermined time range (e.g., 750milliseconds, 500 milliseconds, 100 milliseconds, or the like) beforethe first time (e.g., determining whether the third triggeradvertisement is “sane”).

At block 1916, in accordance with a determination that the second timeis within the predetermined time range before the first time (e.g., ifthe predetermined time range is 500 milliseconds, the second time isless than 500 milliseconds before the first time), the first electronicdevice forgoes further processing of the user voice input. In someexamples, forgoing further processing of the user voice input includesthe first electronic device forgoing transmitting a request to thecontext collector for an aggregate context of the context-sharing group.

In some of the examples where the first electronic device and the secondelectronic device share a short distance communication connection (e.g.,described above with reference to blocks 1906, 1910, and 1914), at block1918, in accordance with a determination that the third time is withinthe predetermined range before the first time, the first electronicdevice forgoes further processing of the user voice input even if thesecond time is not within the predetermined time range before the firsttime.

In some examples, at block 1920, in accordance with a determination thatthe second time is not within the predetermined time range (e.g., if thepredetermined time range is 500 milliseconds, the second time is equalto or more than 500 milliseconds before the first time), the firstelectronic device continues processing the user voice input. In someexamples, continuing processing of the user voice input includes thefirst electronic device transmitting a request to the context collectorfor an aggregate context of the context-sharing group.

The operations described above with reference to FIGS. 14A-14C, 15A-15B,16A-16E, 17A-17C, 18A-18B, and 19A-19B are optionally implemented bycomponents depicted in FIGS. 1-4, 6A-6B, and 7A-7C. For example, theoperations of process 1400, process 1500, process 1600, process 1700,process 1800, and/or process 1900 may be implemented by system 100. Itwould be clear to a person having ordinary skill in the art how otherprocesses are implemented based on the components depicted in FIGS. 1-4,6A-6B, and 7A-7C.

In accordance with some implementations, a computer-readable storagemedium (e.g., a non-transitory computer readable storage medium) isprovided, the computer-readable storage medium storing one or moreprograms for execution by one or more processors of an electronicdevice, the one or more programs including instructions for performingany of the methods or processes described herein.

In accordance with some implementations, an electronic device (e.g., aportable electronic device) is provided that comprises means forperforming any of the methods or processes described herein.

In accordance with some implementations, an electronic device (e.g., aportable electronic device) is provided that comprises a processing unitconfigured to perform any of the methods or processes described herein.

In accordance with some implementations, an electronic device (e.g., aportable electronic device) is provided that comprises one or moreprocessors and memory storing one or more programs for execution by theone or more processors, the one or more programs including instructionsfor performing any of the methods or processes described herein.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data (e.g., user data, user-specific contextinformation, and/or the like) available from various sources to assistwith/improve the determination of digital assistant responses during avideo communication session. The present disclosure contemplates that insome instances, this gathered data may include personal information datathat uniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, twitter IDs,home addresses, data or records relating to a user's health or level offitness (e.g., vital signs measurements, medication information,exercise information), date of birth, or any other identifying orpersonal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todetermine one or more parameters of a task to be performed by digitalassistant of a user device and/or communal device in response to a userrequest. Accordingly, use of such personal information data enables adigital assistant of a user device to provide a digital assistantresponse (based on the performance of the above task) that is morerelevant and/or useful to users. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure. For instance, health and fitness data may be used toprovide insights into a user's general wellness, or may be used aspositive feedback to individuals using technology to pursue wellnessgoals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof gathering and using user data to assist with/improve thedetermination of digital assistant responses, the present technology canbe configured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services or anytime thereafter. In another example,users can select not to provide user data (e.g., a user's media,contacts, speech profiles, preferences, and/or the like) to assistwith/improve the determination of digital assistant responses. In yetanother example, users can select to prevent the gathering and use ofcertain types/forms of personal information data (e.g., email addresses,home addresses, payment information, and/or the like) for thedetermination of digital assistant responses. In addition to providing“opt in” and “opt out” options, the present disclosure contemplatesproviding notifications relating to the access or use of personalinformation. For instance, a user may be notified upon downloading anapp that their personal information data will be accessed and thenreminded again just before personal information data is accessed by theapp.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data at a city level rather than at an addresslevel), controlling how data is stored (e.g., aggregating data acrossusers), and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, digitalassistant responses can be determined based on non-personal informationdata/user data or a bare minimum amount of personal information and/oruser data, such as the content being requested by the device associatedwith a user, other non-personal information available to the digitalassistant, or publicly available information.

What is claimed is:
 1. A method, comprising: at a first electronicdevice participating in a context-sharing group associated with a firstlocation, wherein the context-sharing group is a collection of at leasttwo electronic devices that each share context information with at leastone other electronic device participating in the collection, and whereinthe collection includes at least a second electronic device and acontext collector: receiving a user voice input, wherein the user voiceinput includes a digital assistant trigger; in response to detecting thedigital assistant trigger, transmitting a first trigger advertisement tothe context collector, wherein the first trigger advertisement indicatesa first time at which the digital assistant trigger ended according tothe first electronic device; receiving, from the context collector, asecond trigger advertisement, wherein the second trigger advertisementindicates a second time at which the digital assistant trigger endedaccording to the second electronic device; determining whether thesecond time is within a predetermined time range before the first time;and in accordance with a determination that the second time is withinthe predetermined time range before the first time, forgoing furtherprocessing of the user voice input.
 2. The method of claim 1, furthercomprising: in accordance with a determination that the second time isnot within the predetermined time range, continue processing the uservoice input.
 3. The method of claim 1, wherein each electronic deviceparticipating in the context-sharing group is connected to a singlewireless network of the first location.
 4. The method of claim 3,wherein the first electronic device transmits the first triggeradvertisement to the context collector via the single wireless network.5. The method of claim 3, wherein the context collector transmits thesecond trigger advertisement to the first electronic device via thesingle wireless network in response to receiving the first triggeradvertisement.
 6. The method of claim 1, wherein the second electronicdevice transmits the second trigger advertisement to the contextcollector in response to detecting the digital assistant triggerincluded in the user voice input.
 7. The method of claim 1, wherein thefirst electronic device and the second electronic device share a shortdistance communication connection, further comprising: in response todetecting the digital assistant trigger, transmitting the first triggeradvertisement to the second electronic device via the short distancecommunication connection; receiving a third trigger advertisement fromthe second electronic device via the short distance communicationconnection, wherein the third trigger advertisement indicates a thirdtime at which the digital assistant trigger ended according to thesecond electronic device; after determining whether the second time iswithin the predetermined time range before the first time, determiningwhether the third time is within the predetermined time range before thefirst time; and in accordance with a determination that the third timeis within the predetermined range before the first time, forgoingfurther processing of the user voice input even if the second time isnot within the predetermined time range before the first time.
 8. Themethod of claim 1, wherein the at least two electronic devices of thecontext-sharing group each automatically share context information withat least one other electronic device participating in thecontext-sharing group in response to undergoing a device state change.9. The method of claim 3, wherein each electronic device participatingin the context-sharing group is connected to the single wirelessnetwork.
 10. The method of claim 1, wherein the first electronic devicejoins the context-sharing group by establishing a communicationconnection with at least one other electronic device participating inthe context-sharing group.
 11. The method of claim 1, wherein thecontext information includes contextual state information correspondingto at least the first electronic device and the second electronicdevice.
 12. The method of claim 1, wherein the context informationincludes device capability information corresponding to at least thefirst electronic device and the second electronic device.
 13. The methodof claim 1, wherein the digital assistant trigger is a word or a phrasethat initiates a dialog session with the digital assistant of the firstelectronic device.
 14. The method of claim 1, wherein context-sharinggroup is a collection of at least two electronic devices that each sharecontext information with at least one other electronic deviceparticipating in the collection.
 15. The method of claim 1, wherein thefirst trigger advertisement includes a confidence score corresponding toa confidence of the first electronic device that the user voice inputincludes a digital assistant trigger word or phrase.
 16. The method ofclaim 2, wherein continue processing of the user voice input includesfirst electronic device transmitting a request to the context collectorfor an aggregate context of the context-sharing group.
 17. The method ofclaim 7, wherein the third time is identical to the second timeindicated by the second trigger advertisement.
 18. The method of claim7, wherein forgoing further processing of the user voice input includesthe first electronic device forgoing transmitting a request to thecontext collector for an aggregate context of the context-sharing group.19. A first electronic device, comprising: one or more processors;memory; and one or more programs, wherein the one or more programs arestored in the memory and are configured to be executed by the one ormore processors, wherein the one or more programs include instructionsfor: while the first electronic device is participating in acontext-sharing group associated with a first location, wherein thecontext-sharing group is a collection of at least two electronic devicesthat each share context information with at least one other electronicdevice participating in the collection, and wherein the collectionincludes at least a second electronic device and a context collector:receiving a user voice input, wherein the user voice input includes adigital assistant trigger; in response to detecting the digitalassistant trigger, transmitting a first trigger advertisement to thecontext collector, wherein the first trigger advertisement indicates afirst time at which the digital assistant trigger ended according to thefirst electronic device; receiving, from the context collector, a secondtrigger advertisement, wherein the second trigger advertisementindicates a second time at which the digital assistant trigger endedaccording to the second electronic device; determining whether thesecond time is within a predetermined time range before the first time;and in accordance with a determination that the second time is withinthe predetermined time range before the first time, forgoing furtherprocessing of the user voice input.
 20. A non-transitorycomputer-readable storage medium storing one or more programs, the oneor more programs comprising instructions, which when executed by one ormore processors of a first electronic device, cause the first electronicdevice to: while the first electronic device is participating in acontext-sharing group associated with a first location, wherein thecontext-sharing group is a collection of at least two electronic devicesthat each share context information with at least one other electronicdevice participating in the collection, and wherein the collectionincludes at least a second electronic device and a context collector:receive a user voice input, wherein the user voice input includes adigital assistant trigger; in response to detecting the digitalassistant trigger, transmit a first trigger advertisement to the contextcollector, wherein the first trigger advertisement indicates a firsttime at which the digital assistant trigger ended according to the firstelectronic device; receive, from the context collector, a second triggeradvertisement, wherein the second trigger advertisement indicates asecond time at which the digital assistant trigger ended according tothe second electronic device; determine whether the second time iswithin a predetermined time range before the first time; and inaccordance with a determination that the second time is within thepredetermined time range before the first time, forgo further processingof the user voice input.